The following bugs were fixed since version 4.1.13:
- bug #4365 Creating bookmark with multiple queries not working
- bug #4372 Changing browser transformation results in unnecessary
table rebuild
- bug #4375 Group two DB, one's name is the prefix of the other one
- bug #4376 [interface] Login fields show in separate line
shared-mime-info 1.3 (2014-04-08)
* Mime-type changes:
- Add Aliases for OpenOffice Base and StarWriter
- Add Apple Keynote 5 mime-type
- Add mimetype for compressed FictionBook2
- Don't recognize all .asc files as application/pgp-encrypted
- Add tree magic for the Kindle e-book reader
- Add LZ4 archive type
- Add PC Engine, GameCube and Wii "ROM" types
- Add audio/x-opus+ogg mime-type
- Add image/webp mime-type
- Prefer application/vnd.ms-asf to video/x-ms-asf
- Add application/x-riff mime-type
- Add JSON mime-type
- Add *.jsm glob for Javascript
- Add magic and glob patterns for compressed x-spss-sav files
- JavaScript and CSS are not subclasses of text/x-csrc
- Remove *.CSSL glob for CSS files
* Call g_type_init() only with older glib
* Fix failures on NetBSD
* Store MEDIA/SUBTYPE.xml files in lowercase
Patch from rudolf via private mail.
2014-03-31 - SkyTools 3.2 - "Hit any user to continue"
= Features =
* scripts/data_maintainer.py: can use csv file as source
* debian: support Postgres 9.3, 9.4
= Minor features =
* londiste: added ignore_truncate handler option
* londiste add-table: added lock_timeout option to avoid possible locking issues
* scripts/data_maintainer.py: added dynamic throttling support (via sql)
* skytools.scripting: added options to lower log level for exceptions
* skytools.scripting: simple retriable execute (for sql)
= Fixes =
* londiste.create_partition: fixed to avoid deadlocks from concurrent workers
* londiste.handlers.dispatch: fixed "ignore events aiming at obsolete partitions" bug
* pgq.cascade.admin: do not allow subscribing to itself (same node)
* pgq.consumer: fixed RetriableEvent and RetriableWalkerEvent
* skytools.dbstruct: quote sequence names
* skytools.set_tcp_keepalive: add compat with newer OSX, simplify, enable win32
* scripts/data_maintainer.py: fixed to survive null in stats column of sql_modify
* sql/londiste: fixed londiste.table_info trigger issue
* sql/pgq: fix retry-queue vs. newgrants
* sql/pgq: tag pgq.batch_id_seq as dumpable (extension)
= Cleanups =
* londiste.drop_obsolete_partitions: drop tables in alphabetical order (that is from the oldest)
* londiste.handlers: removed duplicate debug logging
* londiste: moved config processing from dispatch to base handler
* pgq.localconsumer: added file path check on config load
* scripts/data_maintainer.py: clean-up
* debian: include data_maintainer3 in package
* Get rid of dictfetch*() usage, it's obsolete.
Collection.
Official low-level client for Elasticsearch. Its goal is to provide common
ground for all Elasticsearch-related code in Python; because of this it tries
to be opinion-free and very extendable. The full documentation is available at
http://elasticsearch-py.rtfd.org/
Collection.
Elasticsearch is a distributed RESTful search engine built for the cloud.
Features include:
* Distributed and Highly Available Search Engine.
* Multi Tenant with Multi Types.
* Various set of APIs
* Document oriented
* Reliable, Asynchronous Write Behind for long term persistency.
* (Near) Real Time Search.
* Built on top of Lucene
* Per operation consistency
* Open Source under Apache 2 License.
APSW provides an SQLite 3 wrapper that provides the thinnest layer over
the SQLite database library possible. Everything you can do from the
SQLite C API, you can do from Python. Although APSW looks vaguely
similar to the PEP 249 (DBAPI), it is not compliant with that API
because instead it works the way SQLite 3 does.
The following bugs were fixed since version 4.1.12:
- bug #4279 CTRL + up or down moves 2 fields
- bug #4336 List server css style wrong
- bug Missing value on the Status > Server page
- bug #4347 Fixed PHP Parse error in Advisor
- bug #4350 Deleting the DB if it is renamed by the same name
- bug #4353 makeProfilingChart is not defined
- bug #4355 Precision specifier for DOUBLE type is truncated
- bug #4346 Incorrect "Export incomplete" message
- bug #4359 Notices on create table page
- bug #4356 GROUPed selects show number of rows as if not grouped
- bug #4357 JS Form submitted on "enter" even if focus is inside a
select field
an API that is compliant with the Python DB API version 2.0. It is written in
pure Python and does not have any dependencies except for the Python Standard
Library.
MySQL Connector/Python includes support for:
* Almost all features provided by MySQL Server up to and including MySQL Server
version 5.5.
* Converting parameter values back and forth between Python and MySQL data
types, for example Python datetime and MySQL DATETIME. You can turn automatic
conversion on for convenience, or off for optimal performance.
* All MySQL extensions to standard SQL syntax.
* Protocol compression, which enables compressing the data stream between the
client and server.
* Connections using TCP/IP sockets and on Unix using Unix sockets.
* Secure TCP/IP connections using SSL.
* Self-contained driver. Connector/Python does not require the MySQL client
library or any Python modules outside the standard library.
* Unknown
Changes 1.2.4:
* Added support for the MySQL read_timeout option.
* Added a workaround so that the MySQL character set utf8mb4 works with Python; utf8 is substituted on the Python side.
* Unified test database configuration, and set up CI testing with Travis.
fixed since version 4.1.9:
- bug #4334 Add event : datepicker won't open
- bug #4338 Fix missing value error while executing SQL query
- TCPDF library is now optional dependency
- bug #4326 Cannot find the import plugins which start with uppercase 'I'
- bug #4301 Grid edit: "SELECT" query is replaced by "UPDATE" query after edit
- bug #4278 reCaptcha re-login requires double effort
- bug #4324 Datepicker not showing up on insert page
- bug #3991 Problem selecting item in select boxes with the ENTER keystroke
in some browsers
- bug #4323 QueryWindow ignores CodeMirror
- bug None of the live charts shown on "Status -> Monitor" (Chrome)
* Add UNLOGGED, COUNTER options to BATCH documentation (CASSANDRA-6816)
* add extra SSL cipher suites (CASSANDRA-6613)
* fix nodetool getsstables for blob PK (CASSANDRA-6803)
* Add CMSClassUnloadingEnabled JVM option (CASSANDRA-6541)
* Catch memtable flush exceptions during shutdown (CASSANDRA-6735)
* Don't attempt cross-dc forwarding in mixed-version cluster with 1.1
(CASSANDRA-6732)
* Fix broken streams when replacing with same IP (CASSANDRA-6622)
* Fix upgradesstables NPE for non-CF-based indexes (CASSANDRA-6645)
* Fix partition and range deletes not triggering flush (CASSANDRA-6655)
* Fix mean cells and mean row size per sstable calculations
(CASSANDRA-6667)
* Compact hints after partial replay to clean out tombstones
(CASSANDRA-6666)
* Log USING TTL/TIMESTAMP in a counter update warning (CASSANDRA-6649)
* Don't exchange schema between nodes with different versions
(CASSANDRA-6695)
* Use real node messaging versions for schema exchange decisions
(CASSANDRA-6700)
* IN on the last clustering columns + ORDER BY DESC yield no results
(CASSANDRA-6701)
* Fix SecondaryIndexManager#deleteFromIndexes() (CASSANDRA-6711)
* Fix snapshot repair not snapshotting coordinator itself (CASSANDRA-6713)
* Support negative timestamps for CQL3 dates in query string
(CASSANDRA-6718)
* Avoid NPEs when receiving table changes for an unknown keyspace
(CASSANDRA-5631)
* Fix bootstrapping when there is no schema (CASSANDRA-6685)
* Fix truncating compression metadata (CASSANDRA-6791)
* Fix SSTable not released if stream session fails before starts
(CASSANDRA-6818)
Hiredis is a minimalistic C client library for the Redis database.
It is minimalistic because it just adds minimal support for the
protocol, but at the same time it uses an high level printf-alike
API in order to make it much higher level than otherwise suggested
by its minimal code base and the lack of explicit bindings for
every Redis command.
Apart from supporting sending commands and receiving replies, it
comes with a reply parser that is decoupled from the I/O layer. It
is a stream parser designed for easy reusability, which can for
instance be used in higher level language bindings for efficient
reply parsing.
Hiredis only supports the binary-safe Redis protocol, so you can
use it with any Redis version >= 1.2.0.
The library comes with multiple APIs. There is the synchronous API,
the asynchronous API and the reply parsing API.
Replace interpreter path in installed file.
Released 2.4.15 2014-03-24
Changes since 2.4.14:
Lib/
* Added missing modules ldap.controls.openldap and
ldap.controls.pwdpolicy to setup.py
* Added missing imports to ldap.controls.pwdpolicy
* Fixed ldap.controls.pwdpolicy.decodeControlValue() to decode
string of digits
* Support for X-SUBST in schema element class LDAPSyntax
* Support for X-ORDERED and X-ORIGIN in schema element class AttributeType
* ldapurl: New scope 'subordinates' defined in
draft-sermersheim-ldap-subordinate-scope
Modules/
* New constant ldap.SCOPE_SUBORDINATE derived from ldap.h for
draft-sermersheim-ldap-subordinate-scope
* Fixed constant ldap.sasl.CB_GETREALM (thanks to Martin Pfeifer)
Functionality Added or Changed
Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control of the block encryption mode and take an optional initialization vector argument:
The new block_encryption_mode system variable controls the mode for block-based encryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a key length of 128 bits and ECB mode.
An optional init_vector argument provides an initialization vector for encryption modes that require it:
AES_ENCRYPT(str,key_str[,init_vector])
AES_DECRYPT(crypt_str,key_str[,init_vector])
A random string of bytes to use for the initialization vector can be produced by calling the new RANDOM_BYTES() function.
For more information, see Encryption and Compression Functions.
These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for statement-based replication and they cannot be stored in the query cache. Queries that use RANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the query cache.
Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to include any of them generates a warning. In MySQL 5.7, these modes do nothing. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself.
To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether your applications will be affected by the SQL mode changes in MySQL 5.7.
InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL (ALGORITHM=INPLACE) for the following operations:
OPTIMIZE TABLE
ALTER TABLE ... FORCE
ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table)
Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Overview of Online DDL.
On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime.
mysql_install_db provides a more informative diagnostic message when required Perl modules are missing.
The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a future version of MySQL. ALTER IGNORE TABLE causes problems for replication, prevents online ALTER TABLE for unique index creation, and causes problems with foreign keys (rows removed in the parent table).
Bugs Fixed
Functionality Added or Changed
On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime.
Bugs Fixed
InnoDB: A regression introduced by Bug 14329288 would result in a performance degradation when a compressed table does not fit into memory.
InnoDB: The maximum value for innodb_thread_sleep_delay is now 1000000 microseconds. The previous maximum value (4294967295 microseconds on 32-bit and 18446744073709551615 microseconds on 64-bit) was unnecessarily large. Because the maximum value of innodb_thread_sleep_delay is limited by the value set for innodb_adaptive_max_sleep_delay (when set to a non-zero value), the maximum value for innodb_thread_sleep_delay is now the same as the maximum value for innodb_adaptive_max_sleep_delay.
InnoDB: In debug builds, creating a unique index on a binary column, with input data containing duplicate keys, would cause an assertion.
InnoDB: InnoDB would fail to start when innodb_data_file_path specified the data file size in kilobytes by appending K to the size value.
InnoDB: An insert buffer merge would cause an assertion error due to incorrectly handled ownership information for externally stored BLOBs.
InnoDB: Assertion failure in thread thread_num in file ibuf0ibuf.cc line 4080
InnoDB: Failing assertion: rec_get_deleted_flag(rec, page_is_comp(page))
InnoDB: Decreasing the auto_increment_increment value would have no affect on the next auto-increment value.
Replication: The server did not handle correctly the insertion of a row larger than 4 GB when using row-based replication.
Replication: When using row-based replication, an additional auto-increment column on the slave version of a table was not updated correctly; a zero was inserted instead.
Replication: Statements involving the Performance Schema tables should not be written to the binary log, because the content of these tables is applicable only to a given MySQL Server instance, and may differ greatly between different servers in a replication topology. The database administrator should be able to configure (INSERT, UPDATE, or DELETE) or flush (TRUNCATE TABLE) performance schema tables on a single server without affecting others. However, when replicating from a MySQL 5.5 master to a MySQL 5.5 or later slave, warnings about unsafe statements updating Performance Schema tables were elevated to errors. For MySQL 5.6 and later slaves, this prevented the simultaneous use of performance_schema and GTIDs (see Replication with Global Transaction Identifiers, in the MySQL 5.6 Manual).
This fix causes all updates on tables in the performance_schema database to be filtered on the master and not replicated, regardless of the type of logging that is in effect. Prior to this fix, statements using were handled by being marked as unsafe for replication, which caused warnings during execution; the statements were nonetheless written to the binary log, regardless of the logging format in effect.
Existing replication behavior for tables in the INFORMATION_SCHEMA database is not changed by this fix.
For more information, see MySQL Performance Schema.
Compilation failed if MySQL was configured with CFLAGS set to include a -Werror option with an argument.
A shared libmysqld embedded server library was not built on Linux.
While printing the server version, the mysql client did not check for buffer overflow in a string variable.
Contraction information in a collation could be mishandled, resulting in incorrect decisions about whether a character is part of a contraction, and miscalculation of contraction weights.
DROP TRIGGER succeeded even with the read_only system variable enabled.
Updating the Performance Schema setup_instruments table on a replication master caused a slave to exit.
Due to a race condition, it was possible for two threads to end up with the same query ID for different queries.
When run by root, mysqld --help --verbose exited with a nonzero error code after displaying the help message.
MySQL client programs from a Community Edition distribution could not connect using SSL to a MySQL server from an Enterprise Edition. This was due to a difference in certificate handling by yaSSL and OpenSSL (used for Community and Enterprise, respectively). OpenSSL expected a blank certificate to be sent when not all of the --ssl-ca, --ssl-cert, and --ssl-key options were specified, and yaSSL did not do so. To resolve this, yaSSL has been modified to send a blank certificate when an option is missing.
A deadlock error occurring during subquery execution could cause an assertion to be raised.
The Performance Schema stage/sql/Waiting to get readlock instrument is no longer used and has been removed.
For system variables that take a string value, SET statements permitted an unquoted value, but values that contained dots were parsed incorrectly and only part of the value was assigned. For example, SET GLOBAL slow_query_log_file = my_slow.log assigned the value my_slow. Now such values must be quoted or an error occurs.
On Windows, mysql_install_db.pl could be run only from within the bin directory under the installation directory.
The data corruption issue in PostgreSQL 9.3 affects binary replication standbys, servers being recovered from point-in-time-recovery backup, and standalone servers which recover from a system crash. The bug causes unrecoverable index corruption during recovery due to incorrect replay of row locking operations. This can then cause query results to be inconsistent depending on whether or not an index is used, and eventually lead to primary key violations and similar issues. For this reason, users are encouraged to replace each of their standby databases with a new base backup after applying the update.
Other PostgreSQL 9.3-only fixes in this update include:
Make sure that statistics files for dropped databases get deleted
Allow materialized views to be referenced in UPDATE and DELETE queries
Add read-only data_checksum parameter
Prevent erroneous operator push-down in postgres_fdw
This release resolves some other issues in all versions of PostgreSQL, including:
Fix timing consistency issue with NOTIFY
Allow regular expression execution to be cancelled
Improve performance of index checks for newly added rows
Prevent premature walsender disconnection
Prevent memory errors on newer Windows versions
Update timezone files
- Fixed target test failures on Windows.
- Added support for Postgres-XC to the PostgreSQL engine. Sqitch registry
tables are distributed by replication to all data nodes.
- Added support to MariaDB 5.3 and higher to the MySQL engine, thanks to
Ed Silva.
Updating this leaf package during the freeze.
Moneta provides a standard interface for interacting with various kinds of
key/value stores. Moneta supports the well-known NoSQL and document based
stores.
=== 4.8.0 (2014-03-01)
* Add SQL::AliasedExpression#alias alias for #aliaz (jeremyevans)
* Handle SQL::Identifier, SQL::QualifiedIdentifier, and SQL::AliasedExpression objects as first argument to Dataset#graph (jeremyevans)
* Respect qualification and aliases in symbols passed as first argument to Dataset#graph (dividedmind) (#769)
* Recognize new constraint violation error messages in SQLite 3.8.2+ (itswindtw) (#766)
* Use limit strategy to correctly handle limited associations in the dataset_associations plugin (jeremyevans)
* Handle issues in dataset_associations plugin when dataset uses unqualified identifiers for associations requiring joins (jeremyevans)
* Handle fractional seconds in input timestamps in the odbc/mssql adapter (Ross Attrill, jeremyevans)
* Return fractional seconds in timestamps in the odbc adapter (jeremyevans)
* Support :plain and :phrase options to Dataset#full_text_search on PostgreSQL (jeremyevans)
* Use limit strategy to correctly handle filtering by limited associations (jeremyevans)
* Simplify queries used for filtering by associations with conditions (jeremyevans)
* Use an eager limit strategy by default for *_one associations with orders (jeremyevans)
* Support :limit_strategy eager_graph option, for specifying strategy used for limited associations in that eager graph (jeremyevans)
* Add eager_graph_with_options to model datasets, for specifying options specific to the eager_graph call (jeremyevans)
* Handle offsets on *_many associations when eager graphing when there are no associated results (jeremyevans)
* Make Database#register_array_type work without existing scalar conversion proc in the pg_array extension (jeremyevans)
* Handle presence validations on foreign keys in associated objects when creating new associated objects in the nested_attributes plugin (jeremyevans)
* Respect offsets when eager graphing *_one associations (jeremyevans)
* Add association_join to model datasets, for setting up joins based on associations (jeremyevans)
* Add one_through_many association to many_through_many plugin, for only returning a single record (jeremyevans)
* Add :graph_order association option, useful when :order needs to contain qualified identifiers (jeremyevans)
* Add one_through_one association, similar to many_to_many but only returning a single record (jeremyevans)
=== 4.7.0 (2014-02-01)
* Don't swallow underlying exception if there is an exception closing the cursor on PostgreSQL (jeremyevans) (#761)
* Recognize primary key unique constraint violations on MSSQL and SQLAnywhere (jeremyevans)
* Recognize composite unique constraint violations on SQLite (timcraft) (#758)
* Make #* method without arguments on SQL::Function return a Function with * prepended to the arguments (jeremyevans)
* Add #function to SQL::Identifier and SQL::QualifiedIdentifier, allowing for easy use of schema qualified functions or functions names that need quoting (jeremyevans)
* Add SQL::Function#distinct for easier creation of aggregate functions using DISTINCT (jeremyevans)
* Add SQL::Function#over for easier creation of window functions (jeremyevans)
* Don't clear validation instance_hooks until after a successful save (jeremyevans)
* Support :raise_on_save_failure option for one_to_many, pg_array_to_many, and many_to_pg_array associations (jeremyevans)
* Make SQLTime#to_s return a string in HH:MM:SS format, since it shouldn't include date information (jeremyevans)
* Support the Database#tables :schema option in the jdbc adapter (robbiegill, jeremyevans) (#755)
* Automatically rollback transactions in killed threads in ruby 2.0+ (chanks) (#752)
* Add update_or_create plugin, for updating an object if it exists, or creating such an object if it does not (jeremyevans)
* Make auto_validations uniqueness validations work correctly for STI subclasses (jeremyevans)
* Support :dataset option to validates_unique vaildation (jeremyevans)
=== 4.6.0 (2014-01-02)
* Add Database#call_mssql_sproc on MSSQL for calling stored procedures and handling output parameters (jrgns, jeremyevans) (#748)
* Handle RuntimeErrors raised by oci8 in the oracle adapter (jeremyevans)
* Support OFFSET/FETCH on Microsoft SQL Server 2012 (jeremyevans)
* Support :server option for Database#{commit,rollback}_prepared_transaction on PostgreSQL, MySQL, and H2 (jeremyevans) (#743)
* Do not attempt to eager load and raise an exception when doing Model.eager(...).naked.all (jeremyevans)
* Recognize a couple additional disconnect errors in the jdbc/postgresql adapter (jeremyevans) (#742)
pkgsrc change: Add GEM_EXTSDIR support.
== v0.17.1 [2013-12-18] Michael Granger <ged@FaerieMUD.org>
Bugfixes:
- Fix compatibility with signal handlers defined in Ruby. This reverts
cancelation of queries running on top of the blocking libpq API (like
Connection#exec) in case of signals. As an alternative the #async_exec
can be used, which is reverted to use the non-blocking API, again.
- Wrap PQcancel to be called without GVL. It internally waits for
the canceling connection.
Documentation fixes:
- Fix documentation for PG::Connection::conndefaults.
Work around a C-preprocessor macro conflict that breaks the build for some configurations with Microsoft Visual Studio.
When computing the cost of the skip-scan optimization, take into account the fact that multiple seeks are required.
PGUSER, PGGROUP, and PGHOME are all in mk/defaults/mk.conf. They are
also set (?=) in each server Makefile. Worse, PGHOME is set to
varying values. However, the versions in defaults prevail.
Therefore, remove the extra/confusing settings, leaving this as a
user-settable variable with a default. pkg_info -B before and after
shows no related changes, so no PKGREVISION++.
Pointed out by Richard Palo, and ok adam@.
There's a related issue lurking, which is that PGHOME ends up being
/usr/pkg/pgsql, which is not under VARBASE, but I'm letting that be
because a change would be disruptive.
Code optimization and refactoring for improved performance.
Add the ".clone" and ".save" commands to the command-line shell.
Update the banner on the command-line shell to alert novice users when they are using an ephemeral in-memory database.
Fix editline support in the command-line shell.
Add support for coverage testing of VDBE programs using the SQLITE_TESTCTRL_VDBE_COVERAGE verb of sqlite3_test_control().
Update the _FILE_OFFSET_BITS macro so that builds work again on QNX.
Change the datatype of SrcList.nSrc from type u8 to type int to work around an issue in the C compiler on AIX.
Get extension loading working on Cygwin.
Bug fix: Fix the char() SQL function so that it returns an empty string rather than an "out of memory" error when called with zero arguments.
Bug fix: DISTINCT now recognizes that a zeroblob and a blob of all 0x00 bytes are the same thing. Ticket [fccbde530a]
Bug fix: Compute the correct answer for queries that contain an IS NOT NULL term in the WHERE clause and also contain an OR term in the WHERE clause and are compiled with SQLITE_ENABLE_STAT4. Ticket [4c86b126f2]
Bug fix: Make sure "rowid" columns are correctly resolved in joins between normal tables and WITHOUT ROWID tables. Ticket [c34d0557f7]
Bug fix: Make sure the same temporary registers are not used in concurrent co-routines used to implement compound SELECT statements containing ORDER BY clauses, as such use can lead to incorrect answers. Ticket [8c63ff0eca]
Bug fix: Ensure that "ORDER BY random()" clauses do not get optimized out. Ticket [65bdeb9739]
Bug fix: Repair a name-resolution error that can occur in sub-select statements contained within a TRIGGER. Ticket [4ef7e3cfca]
Bug fix: Fix column default values expressions of the form "DEFAULT(-(-9223372036854775808))" so that they work correctly, initializing the column to a floating point value approximately equal to +9223372036854775808.0.
--[ Redis 2.8.7 ] Release date: 5 Mar 2014
# UPGRADE URGENCY: LOW for Redis, LOW for Sentinel. However this release adds
new features so users may want to upgrade in order to
exploit the new functionalities.
* [FIX] Sometimes the absolute config file path was obtained in a wrong way.
This happened when there was a "dir" directive inside the config file
and at the same time the configuration file was given as a relative
path to redis-server or redis-sentinel executables.
* [FIX] redis-cli: Automatically enter --slave mode when SYNC or PSYNC are
called during an interactive session.
* [FIX] Sentinel "IDONTKNOW" error removed as it does not made sense with the
new Sentinel design. This error was actually a fix for a design error
in the first implementation of Sentinel.
* [FIX] Sentinel: added a missing exit() call to abort after config file
checks at startup. This error was introduced with an improvement in
a previous 2.8 release.
* [FIX] BITCOUNT: fixed unaligned access causing issues in sparc and other
archs not capable of dealing with unaligned accesses. This also makes
the code faster in archs where unaligned accesses are allowed.
* [FIX] Sentinel: better nodes fail over start time desynchronization to avoid
split-brain during the voting process needed to get authorization to
fail over. This means the system is less likely to need to retry
and will fail over faster. No changes in behavior / correctness.
* [FIX] Force INFO used_memory_peak to match peak memory. This generated some
confusion among users even if it was not an actual bug.
* [NEW] Sentinel unit tests and framework. More tests needed and units must
be improved in order to have less false positives, but it is a start
and features a debugging console that is useful to fix tests or to
inspect bugs causing tests failures.
* [NEW] New Sentinel events: +/-monitor and +set used to monitor when an
instance to monitor is added or removed, or when a configuration
is modified via SENTINEL SET.
* [NEW] Redis-cli updated to use SCAN instead of random sampling via
RANDOMKEY in order to implement --bigkeys feature. Moreover the
implementation now supports pipelining and reports more information
at the end of the scan. Much faster, much better. A special thank
you to Michael Grunder for this improvement.
* [NEW] redis-cli now supports a new --intrinsic-latency mode that is able
to meter the latency of a system due to kernel / hypervisor.
How to use it is explained at http://redis.io/topics/latency.
* [NEW] New command BITPOS: find first bit set or clear in a bitmap.
* [NEW] CONFIG REWRITE calls are now logged.
--[ Redis 2.8.6 ] Release date: 13 Feb 2014
# UPGRADE URGENCY: HIGH for Redis, LOW for Sentinel. Redis users using Lua
scripts with EVALSHA and attached slaves and/or AOF
persistence should consider upgrading ASAP.
* [FIX] Fixed an critical EVALSHA script cache bug: scripts executed may not
propagate to AOF / Slaves correctly under certain conditions.
See issue #1549 at Github for more information.
* [FIX] Fixed multiple bugs resulting into closing the link with master or slave
during replication without good reasons. This will result in useless
resynchronizations, or infinite loops where the replication link can't
be established.
* [FIX] Don't count the time needed to populate the buffers of clients waiting
in MONITOR mode when populating the Slow Log entries.
* [NEW] AOF write errors (like no space on device) no longer abort Redis if the
fsync policy is none or every second. The database enters a read-only
mode where every write is refused with an error. Normal operations are
restored as soon as Redis is able to append again data to the AOF file.
* [NEW] Sentinel now accepts SHUTDOWN command.
--[ Redis 2.8.5 ] Release date: 4 Feb 2014
# UPGRADE URGENCY: HIGH for Redis, LOW for Sentinel. Redis users using Lua
scripts with expires, and Redis users relying on the
ability of Redis to block writes on RDB saving errors
should plan to upgrade ASAP.
* [FIX] Fixed a replication bug caused by Lua scripts + expired keys: keys could
expire in the middle of scripts causing non-deterministic behavior.
* [FIX] MISCONFIG error if condition fixed, the server was no longer able
to stop writes on RDB misconfiguration after this error was introduced.
* [FIX] REDIS_AOF_REWRITE_MIN_SIZE is now 64mb like example redis.conf default.
* [FIX] Perform fflush() before fsync() in rio.c (bug without actual effects).
* [FIX] Don't log MONITOR clients as disconnecting slaves.
* [FIX] SENTINEL MASTER arity check fixed. Crashed the Sentinel instance when
the command was given without arguments.
* [NEW] Allow CONFIG and SHUTDOWN while in stale-slave state.
* [NEW] Support for configurable TCP listen(2) backlog size.
* [NEW] redis-cli supports SCAN via the --scan and --pattern options.
* [NEW] SENTINEL SET master quorum via runtime API implemented.
--[ Redis 2.8.4 ] Release date: 13 Jan 2014
# UPGRADE URGENCY: MODERATE for Redis and Sentinel.
* [FIX] Makefile compatibility with non common make variants improved.
* [FIX] SDIFF crash in very unlikely to trigger state fixed.
* [FIX] Config rewriting fixed: don't wipe options unknown to the rewrite
process.
* [FIX] Set TCP port to 0 works again to disable TCP networking.
* [FIX] Fixed replication with old Redis instances as masters by not
sending REPLCONF ACK to them.
* [FIX] Fix keyspace notifications rewrite and CONFIG GET output.
* [FIX] Fix RESTORE TTL handling in 32 bit systems (32 bit overflow).
* [NEW] Sentinel now has a run time configuration API.
* [NEW] Log when we lost connection with master or slave.
* [NEW] When instance is turned from slave to master now inherits the
old master replication offset when possible. This improves the
Sentinel failover procedure.
The following bugs have been fixed since the release of version 4.1.7:
- bug #4279 CTRL + up or down moves two fields (part one)
- bug #4294 output as text radio clickable for "OpenDocument Text" export
- bug #4297 DROP DATABASE tick box in export no longer works
- bug #4291 Unable to export comments in OpenDocument text format
- bug #4299 Deletion even when the user says "No" to the confirmation message
- bug #4303 "New" link in navi panel is shown even if no privileges
- bug #4302 Some params are being omitted from microhistory
- bug #4298 Missing validation on Import CSV: "Columns enclosed with" and
"Columns escaped with"
- bug #4040 Fatal error while resetting settings
- bug #4305 JS error when editing procedure from nav panel
- bug #4308 Edit routine form submitting when pressing enter
- bug #4307 Nav: "Columns" won't expand with specific schema
- bug #4276 Login loop on session expiry
- bug #4249 Incorrect number of result rows for SQL with subqueries
- bug #4275 Broken Link to php extension manual
- bug #4053 List of procedures is not displayed after executing with Enter
- bug #4081 Setup page content shifted to the right edge of its tabs
- bug #4284 Reordering a column erases comments for other columns
- bug #4286 Open "Browse" in a new tab
- bug #4287 Printview - Always one column too much
- bug #4288 Expand database (+ icon) after timeout doesn't do anything
- bug #4285 Fixed CSS for setup
- Fixed altering table to DOUBLE/FLOAT field
- bug #4292 Success message and failure message being shown together
- bug #4293 opening new tab (using selflink) for import.php based actions
results in error and logout
Based on PR pkg/48639 by rudolf.
SkyTools is a package of tools in use in Skype for replication and failover.
It also includes a generic queuing mechanism called PgQ and a utility
library for Python scripts, as well as a script for setting up and managing
WAL based standby servers.
PgQ is a queuing system written in PL/pgSQL, Python and C code. It is based
on snapshot-based event handling ideas from Slony-I, and is written for
general usage. PgQ provides an efficient, transactional, queueing system
with multi-node support (including work sharing and splitting, failover and
switchover, for queues and for consumers). PgQ is split into 3 layers:
Producers, Ticker and Consumers.
Londiste is a replication tool written in Python, using PgQ as event
transport.
Walmgr is a script that will setup WAL archiving, does the initial backup,
and runtime WAL archive and restore. It can also be used for
up-to-last-second partial file copying, so that less than the whole file is
lost in case of loss of the master database server.
Lib/
* Added ldap.controls.openldap.SearchNoOpControl
* New method ldap.async.AsyncSearchHandler.afterFirstResult()
for doing something right after successfully receiving but before
processing first result
* Better log data written when invoking ldap.LDAPLock.acquire() and
ldap.LDAPLock.release()
* LDAPObject and friends now pass `desc' to ldap.LDAPLock() which
results in better logging
* ldapobject.ReconnectLDAPObject now uses internal class-wide
lock for serializing reconnects
* Method signature of ReconnectLDAPObject.reconnect() changed to be able
to call it with separate retry_max and retry_delay values
Modules/
* Added support for retrieving negotiated TLS version/cipher
with LDAPObject.get_option() with the help of upcoming OpenLDAP libs
Upstream changes:
0.41 - 2013-07-29, H.Merijn Brand
* Use File::Spec->tmpdir () for universal existing folder
Note that huge $TMP folders may cause the test to run slow
* Use File::Spec::rel2abs () instead of abs_path and hoops
* Guard against parallel testing, which is unsupported
* Guard against streaming tests (they PASS on the DBI-devel)
0.40 - 2013-07-23, H.Merijn Brand
* Fix version references in doc
* Fix tests for Windows
0.39 - 2013-06-28, H.Merijn Brand
* Use f_file in docs. file is deprecated
* DBD::CSV's repository moved to github
* Add test for row-completeness
* Fix UTF-8 tests to better follow Text::CSV_XS auto-encoding
* Require more recent versions of low level modules that fixe
issues reported for DBD::CSV
* Development will also do mosts tests with DBI_SQL_NANO=1
* Added support for f_dir_search from DBD::File (in fact DBI was
changed to feature this for DBD::CSV :)
* Fix test relying on spell-error in DBI's error message
* Document csv_class (still undertested)
This update fixes CVE-2014-0060, in which PostgreSQL did not properly enforce the WITH ADMIN OPTION permission for ROLE management.
This update also fixes some issues which affect binary replication and row locking, and can cause recoverable data corruption in some cases.
In addition to the above, the following issues are fixed in this release:
Fix WAL logging of visibility map change
Make sure that GIN indexes log all insertions
Get pause_at_recovery_target to pause at correct time
Ensure walreceiver sends hot-standby feedback messages on time
Prevent timeout interrupts from taking control away from mainline code
Eliminate several race conditions
Fix some broken HINTs in error messages
Prevent server lockup on SSL connection loss
Fix two Unicode handling issues
Prevent crash on certain subselect syntax
Prevent crash on select from zero column table
Fix two bugs with LATERAL
Fix issue with UNION ALL, partitioning, and updates
Ensure that ANALYZE understands domains over ranges
Eliminate permissions check when using default tablespace
Fix memory leakage in JSON functions
Allow extensions with event triggers
Distinguish numbers correctly in JSON output
Fix permissions for pg_start_backup() and pg_stop_backup()
Accept SHIFT_JIS as locale name
Fix .* expansion for SQL function variables
Prevent infinite loop on some COPY connection failures
Several fixes for client issues on Windows
Enable building PostgreSQL with Visual Studio 2013
Update time zone files for recent changes
Changes since version 4.0.10:
- This release contains many improvements and bug fixes. With this
release the minimum supported PHP version is now 5.3 and the minimum
MySQL version is 5.5.
- Allow specifying a port when connecting to the controlhost
- User interface improvements to server privileges, view creation, the
Operations tab, Relation View, and when creating new users
- Added support for AES_ENCRYPT on BLOB columns
- Added support for relations with ndbcluser
- Added optional ReCAPTCHA support during login
- Added support for fractional seconds in time, datetime, and timestamp
columns
- Added find and replace by column
- Added the Error Reporting Component, an optional feature allowing
users to report certain errors directly to the phpMyAdmin bug team
- Added configurable menus (so an administrator can hide certain features)
0.991 2014-01-16T23:24:33Z
- Greatly simplified determining the Firebird ISQL client. It no longer
tries so hard to find a full path, but does seach through the path list
for a likely candidate between fbsql, isql-fb, and isql (or equivalents
ending in .exe on Windows).
- Removed a bunch of inappropriately pasted stuff from the Firebird
tutorial, and updated it a bit.
- `HEAD` and `ROOT` are now recognized as aliases for `@HEAD` and
`@ROOT`, when querying the database, too. That means that `revert --to
HEAD` now works the same as `revert --to @HEAD`, as had been expected
in v0.990.
- Eliminated "use of uninitialized value" warnings when database
connections fail.
- Reduced the minimum required DBD::Firebird to v1.11.
- Fixed the `--verbose` option to the `target` command.
- Eliminated more user-configuration issues in tests, thanks to
chromatic.
- Fixed test failures when the `$PGPASSWORD` environment variable is set,
thanks to Ioan Rogers's test smoker.
0.990 2014-01-04T01:14:24Z
[New Features]
- Added new command and feature: `target`. Use it to manage multiple
database targets, each with an associated URI and, optionally, a
registry name and command-line client. Inspired by Git remotes.
- Added Firebird engine. Three cheers to Ștefan Suciu for this
contribution!
- Added support for the generation of arbitrary scripts from templates to
the `add` command. Just add template files to subdirectories of the
`templates` directory, and scripts will be created in a directory of
the same name based on those templates.
- Added `--open-editor` option (and aliases) to the `add` and `rework`
commands. This option will open the newly-added change scripts in the
preferred editor. Thanks to Thomas Sibley for the patch!
[Improvements]
- Improved database driver loading to ensure the proper version of the
driver is required.
- Non-fatal but possibly unexpected messages -- which correspond to exit
value 1 -- now send their messages to STDOUT instead of STDERR, and
respect the `--quiet` option. Thanks to @giorgio-v for the report!
- Added or replaced the `--target` option to commands that connect to a
database to specify the name of target managed by the new `target`
command or a database URI.
- `HEAD` and `ROOT` are now recognized as aliases for `@HEAD` and
`@ROOT`, respectively, since they are disallowed as change names,
anyway, and folks often use them out of habit from Git.
[Internals]
- Replaced the engine-specific connection attributes with three
attributes use by every engine:
* `target`: The name of a target managed by the new `target` command.
Defaults to a value stored for the `core.$engine.target`
configuration variable. If that variable does not exist, the target
falls back on the stringification of `uri`.
* `uri`: a database URI with the format `db:{engine}:{dbname}` or
`db:{engine}://{user}:{password}@{host}:{port}/{dbname}`. If its
value is not passed to the constructor, a `uri` value is looked up
for the associated `target`. If `target` is not passed or configured,
or if it has no URI associated with it, the `config.$engine.uri`
configuration variable is used. If that value does not exist, the URI
defaults to `db:$engine:`. In any of these cases, if any of the
`--db-*` options are passed, they will be merged into the URI.
* `registry`: the name to use for the Sqitch registry schema or
database, where Sqitch's own data will be stored, as appropriate to
each engine. If its value is not passed to the constructor, a
`registry` value is looked up for the associated `target`. If
`target` is not passed or configured, or if it has no registry
associated with it, the `config.$engine.registry` configuration
variable is used. If no value is found there, it defaults to an
engine-specific value, usually "sqitch".
[Bug Fixes]
- Fixed a bug when installing under local::lib. Thanks to Thomas Sibley
for the pull request!
- Eliminated "Wide character in print" warnings when piping the `log`
command.
- Documented that reworked changes do not have their verify tests run by
the `verify` command. They do run when using the `--verify` deploy
option.
- Removed the documentation for the `add.with_deploy`, `add.with_revert`,
and `add.with_verify` configuration variables, which were never
implemented.
[Deprecations]
- Deprecated engine-specific connection attributes and configuration
variables. See the "Internals" section for their replacements. The
deprecated options are:
* `core.$engine.username`
* `core.$engine.password`
* `core.$engine.db_name`
* `core.$engine.host`
* `core.$engine.port`
* `core.$engine.sqitch_schema`
* `core.$engine.sqitch_db`
- Deprecated all command-specific options with the string "target" in
them, such as `--to-target`, `--upto-target`, etc. They have been
replaced with options containing the string "change", instead, such as
`--to-change` and `--upto-change`. Few people used these options,
preferring their shorter aliases (`--to`, `--upto`, etc.).
- Deprecated the `--deploy-template`, `--revert-template`, and
`--verify-template` options to the `add` command. They are replaced
with a single option, `--use` which takes a key/value pair for the
script name and template path. This makes it useful for arbitrary
script generation, as well.
- Deprecated the `--deploy`, `--revert`, and `--verify` options to the
`add` command, as well as their `--no-*` variants. They are replaced
with two new options, `--with` and `--without`, to which a script name
is passed. These are useful for arbitrary script generation, as well.
- Deprecated the `add.deploy_template`, `add.revert_template`, and
`add.verify_template` configuration settings. They have been replaced
with a section, `add.templates`, which is more general, and supports
arbitrary script generation, as well.
[Incompatibilities]
- Removed the undocumented `--test` option to the `add` command.
- Changed the meaning of `--target` from specifying a change to
specifying a deployment target. Use the new `--change` option to
specify a change.
0.983 2013-11-21T21:50:12Z
- Fixed "Use of uninitialized value" in the MySQL engine. Thanks to
Jean-Michel REY for the report.
- All tests now protect against failures due to the presence of the
`$SQITCH_CONFIG` environment variable (issue #114).
- The installer now respects the `distdir` option to `Build.PL` when
searching for existing templates. Important for packaging.
- Fixed the error "Table 'sqitch.changes' doesn't exist" when deploying
to a MySQL database that exists but has not been initialized. Thanks to
Jean-Michel REY for the report!
- Refactored the handling of the C<--log-only> option so it sets an
engine attribute, rather than passing the flag to a whole stack of
method calls.
- Fixed "Argument "en_us" isn't numeric" error on Windows.
- Now using `LC_ALL` instead of `LC_MESSAGES` when setting the locale, as
the latter is not present on Windows.
- The sqitch-pg RPM now requires DBD::Pg 2.0.0 or higher.
- Improved handling of invalid command names so that the error message is
less ambiguous when triggered by a Perl parse error.
- Added `-m` as an alias for `--note`, for you Git folks out there.
- Added exception handling to the Postgres and Oracle engines to avoid
unexpected errors when deploying to a database that has not been
deployed to before.
- Updated detection of an uninitialized database to double-check with the
engine that it really thinks it's uninitialized, not just that the
"changes" table is missing. This should catch the case where the
database has its own "changes" table unrelated to Sqitch.
0.982 2013-09-11T18:26:07Z
- Errors thrown by Template toolkit are no longer silently ignored.
- Variables passed to change templates are now cloned before the
execution of each template. This prevents one template from deleting
variable values another template might also need.
- Fixed "The getpwnam function is unimplemented" errors on Win32.
- No longer runs revert scripts when deploying with `--log-only` and a
verify script fails, as that could lead to data loss (yikes!). Thanks
to BryLo for the report (issue #112).
0.981 2013-09-06T00:22:26Z
- Now use Encode::Locale to try to decode the user's full name from the
system encoding when fetched from the system on all OSes. Note that
this is not necessary if the `user.name` config is explicitly set, as
recommended. Issue #107.
- Removed the special-case handling of the user's full name fetched from
the system on OS X.
- Added call to `sleep` to test in an attempt to fix SQLite failures.
- The SQLite engine now requires that the SQLite client be 3.3.9 or
later, for support of the `-bail` option.
- Bug fix: The MySQL engine now properly uses the host, port, and
password options when connecting to the database. Thanks to vreb87 for
the report!
0.980 2013-08-28T21:40:00Z
- Changed the default SQLite Sqitch database name from
`$dbname-sqitch.$suffix` to `sqitch.$suffix`. The `$suffix` still
comes from the destination database name. This breaks compatibility
with previous releases. If you need the old name, set it with
`sqitch config core.sqlite.sqitch_db $dbname`.
- Fixed encoding of the user's full name when fetched from the system on
OS X. Thanks to Tomohiro Hosaka for the pull request!
- Fixed test failures when DBD::SQLite is installed but compiled with
SQLite 3.7.10 or lower.
- Fixed a bug where declaring a dependency on a reworked change would
incorrectly result in the error "Key "foo" matches multiple changes".
Thanks to BryLo for the report (issue #103).
- Modified tests to allow them to run in parallel without stomping on
each other.
- Bundling of options, such as `-vvv`, now works properly (issue #108).
- Added alias `--get-regexp` for `--get-regex` to the `config` command.
This brings it in line with the documentation for the `config` command
(Issue #110).
- Fixed all of the `config` command actions that contain a dash so that
they actually work. Thanks to Ștefan Suciu for the report (issue #110).
- All leading and trailing white space is now trimmed from plan notes,
rather than just vertical white space. Thanks to Ronan Dunklau for the
report (issue #106).
- The `status` command now notices if the specified database is
uninitialized and says as much, rather than dying with an SQL error
(issue #109).
- When reading the user's username from the system Sqitch now uses
Encode::Locale to try to decode the value from the system encoding.
Issue #107.
- Compatibility change: Changed the location and name of script template
files. Previously they were called `deploy.tmpl`, `revert.tmpl`, and
`verify.tmpl`, and they lived in the `templates` subdirectory of the
system-wide and user-specific configuration directories. They now live
in subdirectories of the `templates` directory named for each action
(deploy, revert, and verify), and with file names matching engine names
(`pg.tmpl`, `sqlite.tmpl`, `oracle.tmpl`, and `mysql.tmpl`). The
installer will move old files from the system-wide config directory
(`sqitch --etc-path`) to their new homes, named `pg.tmpl` and
`sqlite.tmpl`. It assumes no customizations exist for Oracle. If that's
not true in your case, simply copy the `pg.tmpl` files to
`oracle.tmpl`.
- Added the `--template-name` option to the `add` command. By default, it
looks for templates named for the current engine. The option allows for
the user of task-specific templates. For example, if you create
templates named `createtable.tmpl` in the `deploy`, `revert`, and
`verify` subdirectories of `~/.sqitch/templates`, You can specify
`--template-name createtable` to use those templates when adding a
change.
- Added the `--exists` option to the `show` command.
- Fixed the `--set` option to the `add` command so that duplicate keys
have their values passed to the template as an array, as documented.
- If Template::Toolkit is installed, the `add` command will use it for
processing templates instead of Template::Tiny. This makes it easy to
upgrade the templating environment just by installing a module.
0.973 2013-07-03T13:47:22Z
- Now Require DBD::SQLite compiled with SQLite 3.7.11 or higher. It
always has, but now it throws a meaningful exception if an older
version is compiled into DBD::SQLite. Thanks to Damon Buckwalter for
the report.
- When a deploy fails because of missing dependencies, the list of
missing dependencies no longer contains duplicates. Thanks to Damon
Buckwalter for the report.
0.972 2013-05-31T23:26:52Z
- Fixed test failures on Windows.
- Fixed locale configuration on Windows so that `sqitch` will actually
run, rather than exiting with an error about `LC_MESSAGES` not being
set.
- Fixed a test hang on Windows when DBD::Oracle is installed but the
Oracle libraries (`OCI.dll`) are not or cannot be found. This was
triggering a UI dialog that did not dismiss itself. Using Win32::API
to work around this issue. Thanks to Jan Dubois for the fix.
0.971 2013-05-18T21:08:51Z
- Removed most uses of the smartmatch operator, since as of Perl 5.17.11
it is marked as experimental, and silenced the warning where it is
still used.
- Added 0.1s sleep between logging changes back-to-back in the engine
tests, mostly to try to get SQLite to generate different timestamps.
Pretty sure the recent test failures have been due to the passage of
less than a millisecond between the two inserts.
- Added the `shell` and `quote_shell` methods to Sqitch.pm for shelling
out a command.
- Sqitch now shells out to an editor when opening a file for the user to
edit. For example, if the `$EDITOR` environment variable is set to
`"emacs -nw"`, it will now work. Thanks to Florian Ragwitz for the
report (issue #80).
- Removed the pod-checking tests from the distribution.
0.970 2013-05-09T00:21:06Z
- Fixed the default ordering of changes displayed by the `plan` command.
They are now ascending by default.
- Switched to PerlIO::utf8_strict for fast character encoding and
decoding.
- The help emitted when an unknown option is passed to `sqitch` now
consists of a usage statement and brief table of options, rather than
the entire man page.
- Added the project name in a header to the output of the `plan` command.
- Added the Oracle engine.
- Added `sqitchtutorial-oracle.pod`, a Oracle-specific variant of
`sqitchtutorial.pod`.
- Added missing version declaration to the App::Sqitch::Plan::* modules.
- Devel::StackTrace 1.30 is now properly required (it was previously
recommended).
- The `--show-tags` and `--show-changes` options to the `status` command
now show the changes when the project plan cannot be found (issue #90).
0.965 2013-04-23T16:25:59Z
- Fixed failing test due to line-ending character variations on Windows.
Many thanks to Jan Dubois for the testing help.
- Replaced all uses of `$/` in output to `"\n"`. Thanks to Jan Dubois for
pointing out the incorrect use of `$/`.
- Fixed build error that prevented installation on Perl 5.10 when the
parent module was not installed.
0.964 2013-04-15T18:47:30Z
- Fixed test failures on Perl versions lower than 5.14 when DBD::SQLite
or DBD::Pg is not installed.
- Removed DBD::SQLite from the list of build dependencies.
- Fixed test failures due to encoded (wide-character) warnings on
triggered on systems with non-english locales. Thanks to Alexandr
Ciornii for the smoke testing that revealed this issue.
- Removed overriding of Throwable's `previous_exception` in
App::Sqitch::X on Throwable 0.200007 and higher, where it is no longer
needed.
- Changed test comparing file contents that fails on Windows to do a
looser comparison and hopefully fix the test failure.
0.963 2013-04-12T19:11:29Z
- Fixed a test failure when Git is in the execution path and the test is
not run from a Git checkout.
- Added `plan` to `sqitchchanges`, the contents of which are shown when
Sqitch is run with no command.
- Removed the unique constraint on tag names in the database, as it
prevented two projects from having the same tag name. Replaced it with
a unique constraint on the project and tag names. Folks with production
PostgreSQL installs should run these queries:
ALTER TABLE sqitch.tags DROP CONSTRAINT tags_tag_key, ADD UNIQUE(project, tag);
COMMENT ON COLUMN sqitch.tags.tag IS 'Project-unique tag name.';
- Fixed failing tests when DBD::SQLite is not installed.
- Removed dependency on Git::Wrapper. The `checkout` command does things
very simply, and we already have tools for running command-line
applications. So we just take advantage of that. The code is no more
complicated than it was before.
- Added the `core.vcs.client` configuration setting. Defaults to `git`
(or `git.exe` on Windows).
0.962 2013-04-10T17:10:05Z
- Fixed failing test on Perl 5.12 and lower.
- Fixed the French translation by re-encoding it in UTF-8 (Ronan
Dunklau).
- Fixed the loading of the editor with placeholder text to properly
encode that text as UTF-8 (Ronan Dunklau).
COMPATIBILITY WARNING:
The bug fix "LDAP.pm: new parameter bind(sasl_host => SASLHOST)"
is an incompatible change that may break some corner-case configurations
* that use SASL for authentication and
* where the SASL host name differs from the host name connecting to.
The incompatible change was necessary as it was not possible to fix
the issue which was introduced in perl-ldap 0.37 in a compatible way.
See Net::LDAP's manual page for the details on "sasl_host".
Bug Fixes:
* RT#91210: Paged.pm: fix example code
* RT#90459: LDAP.pm: make LDAPS work after LDAP+start_tls
* RT#91177: AD.pm: fix change_ADpassword()
* RT#88792: Constant.pm: add LDAP_CONTROL_SORTRESPONSE
* LDAP.pm: new parameter bind(sasl_host => SASLHOST)
* Entry.pm: ignore options when update()ing LDIF
* Entry.pm: let update() fail correctly on illegal target
* RT#86053: FAQ.pod: fix spelling error
* *.{pm,pod}: lots of more grammar & spelling fixes / harmonizations
* RT#85941: LDAP.pm: new method data_ready()
* RT#84886: Control/Relax.pm: fix typo in documentation
* RT#84410: PersistentSearch.pm: use $message->pop_entry() in example
* RT#84774: Constant.pm: unbreak Novell eDirectory constants
* RT#73202: LDIF.pm: Base64-encode values ending in spaces
* RT#83815: fix typo/bug in example for root_dse
* various clarification & fixes in documentation
* t/7{1pre,2post}read.t: don't use deprecated methods
* fix PreRead & PostRead controls
* AD.pm: fix typo in documentation
* RT#81380: in Filter.pm unescape hexpairs and ( ) \ * only
* tests: compare files in "text mode"
* Makefile.PL: mention all requirements for tests
* t/07filtermatch.t: use core module Text::Soundex instead of String::Approx
* Message.pm: fix regression w.r.t. Net::LDAP::Message::Dummy
* RT#80482 fix display of =item inet6 in LDAP.pod
* RT#66753: new key & cert for SSL server tests
* RT#79763 Net::LDAP::Util's $VERSION increased
* t/06constant.t: numbering glitch in t/06constant.t
* FilterMatch.pm: fix mapping of greaterOrEqual
* FAQ.pod: small fixes
* RT#79763 extend ldap_explode_dn() for RFC 4514
* RT#77291 canonicalize host name with ldapi://
* LDAP.pm: don't try to set errors on undefined objects
* Util.pm: fix bug in escape_dn_value()
* t/55ssl.t: fix typos in output text
* LDIF.pm: with encode => 'canonical', do mbcescape DNs
* the usual typo fixes in docs
* contrib/ldifdiff.pl: fix POD
* Intermediate/SyncInfo.pm: fix newcookie() method
* LWP/Protocol/ldap.pm: complete overhaul
* LDAP.pm: unbreak - make done a real sub
* Message.pm: fix typo, i.e. add forgotten ';'
* RT#72108 fix non-blocking IO with SSL
* RT#74572 fix $entry->update($ldif)
* RT#74759 fix POD spelling/grammar errors
* RT#77180 use "sslv23" instead of "sslv2/3" for sslversion
* work around a warning in Authen::SASL::Perl <= 2.1.5
* various typo fixes in documentation
* un-break certificate verification
* fixes for the ProxyAuthorization control
* fix typos & spelling errors in POD
Enhancements:
* Filter.pod: remove misleading text
* typo fixes
* RT#91156: add META.json
* DSML.pm, Protocol/ldap.pm: use MIME::Base64::decode()
* make MIME::Base64 mandatory
* README: update optional modules, slight reorganization
* Entry.pod: update documentation of N:L:E->update
* Makefile.PL: require Text::Soundex for tests
* LDAP.pm: use data_ready() in process()
* Util.pm: simplify return on error
* Constant.pm: add constant LDAP_CONTROL_NOOP
* Schema.pm: call isa() as recommented in UNIVERSAL.pm
* FAQ.pod: add more directory servers
* t/07filtermatch.t: skip some tests unless Text::Soundex is installed
* t/74matchedvalues.t: new, tests for MatchedValues control
* t/73assert.t: new, tests for Assertion control
* LDIF.pm: overhaul
- flexibilize mode handling, accept PerlIO layers
- get rid of dependency on Symbol & SelectSaver
- convert _write_... to object methods
- use indirect file handles for URLs
* LWP/Protocol/ldap.pm: use regex as 1st arg to split()
* Control/ManageDsaIT.pm: update documentation & simplify a bit
* Control/Relax.pm: new
* Constant.pm: add LDAP_CONTROL_RELAX
* LDAP.pod: omit space from filter in synopsis
* FAQ.pod: don't talk of "2 lines" when there's only one
* Extra/eDirectory.pm: fix typo, space police
* FAQ.pod: mention Dancer::Plugin::LDAP, update example
* Extra/eDirectory.pm: new; extensions for eDirectory
* Constant.pm: add constants for Novell eDirectory
* LDIF.pm: clean up handling of mode parameter
* LDIF.pm: partially support controls when reading
* Util.pm: add time conversion functions
* Makefile.PL: update recommends, add comments on core modules
* FAQ.pod: update info on required/optional modules
* LDAP.pod,FAQ.pod: harmonize documentation of scope values
* Filter.pm: new method negate()
* Util.pm: new function ldap_url_parse()
* RT#77716: LDAP.pm: new option keepalive for new()
* LDAP.pm: convert scheme to lowercase in new()
* FAQ.pod: how to search all members of a large AD group
* FAQ.pod: how to do nested group searches in AD
* add tests for PreRead & PostRead controls
* FAQ.pm: example for certificateExactMatch
* coding style overhaul:
* use single-quoted strings where possible
* 2 SPACEs before postfix if,unless,or,and
* SPACE after comma
* SPACE between if,elsif,unless,while,for and (
* make private lexical variables more private
* unquote identifiers before =>
* unquote identifiers used as hash keys
* Schema.pod: document attribute_syntax()
* contrib/schema2ad.pl: new, convert schema file to something AD can digest
* Makefile.PL: make dependencies reflect reality better
* LDAP.pm: avoid warning in new() that might have occurred in corner cases
* add constant LDAP_PROXY_AUTHZ_FAILURE
* FilterMatch.pm: complete overhaul
- update matching rules known in OpenLDAP
- support matching rules for extensibleMatch
- avoid warning if no matching rule is found
- add specific implementations for a lot of rules
* global overhaul towards Perl 5.8 features
- declare @ISA and $VERSION as package-local
- replace 'use vars' by 'our'.
* Makefile.PL: overhaul
* tests: cleanup & extensions
- convert to Test::More
- t/common.pl: allow client() to take options for Net::LDAP
- t/common.pl: get rid of local compare function
- t/03schema.t: overhaul, update data/schema.in
- t/07filtermatch.t: new, tests for Net::LDAP::FilterMatch
- t/40connect.t: new, test for IPv4 / IPv6 connections
- reorganize servers tests: rename t/5X*.t -> t/4(X+1)*.t
- t/47ipc.t: add TLS tests
- t/60cancel.t: new, tests for Net::LDAP::Extension::Cancel
- t/70sortctrl.t: make it a server test & add multi-attribute testcase
* ASN.pm: adapt to RFC 4511
* Extension/{SetPassword,Refresh}.pm: polish ASN.1 definition
* LWP/Protocol/ldap.pm: respond with requested MIME type
* LWP/Protocol/ldap.pm: document 'x-format' URI extension
* LWP/Protocol/ldap.pm: add DSMLv1 as output format
* test routines updated to work with recent OpenLDAP
* removed trailing spaces
* support OpenLDAP extension: scope => "children"
* more feature constants in Net/LDAP/Constant.pm
* new features & documentation for LWP/Protocol/ldap.pm
* LWP/Protocol/ldapi.pm: support ldapi:// URIs with LWP
* contrib/LWPsearch.pl: demo program for LWP::Protocol::ldap*
* update link list in the FAQ
* update references to RFCs
* FAQ.pod: update URLs a bit more
* RT#77458 re-work IPv6 support
* Don't accumulate intermediate messages passed to a callback.
* slightly extend Net::LDAP::Entry->update() and document it
* convenience alias done() for Net::LDAP->unbind()
* various updates to the FAQ
* MANIFEST.SKIP: sync with Perl 5.14.2's ExtUtils version
* Makefile.PL: update resource info on repository
* new extended operation Net::LDAP::Extension::Cancel
* new control Net::LDAP::Control::MatchedValues
* new control Net::LDAP::Control::Assertion
* update reference documents in POD
* extend documentation for Pre-Read & Post-Read controls
* add error string for LDAP_VLV_ERROR
* add result codes for VLV and cancel
* add constant for DontUseCopy control
* add constant for PermissiveModify control
* Fix copy & paste errors in Net::LDAP::Message
* Check whether LDAP socket object has a peerhost() method defined
before calling it. This fixes SASL authentication over UNIX domain
(ldapi://) sockets. [Chris Mikkelson]
* use of non-localised $_ in Net::LDAP::Constant causes prolems in lemonldap-ng [Damyan Ivanov]
* Added cn,o,ou to the default set of case-insensitive attributes [Kartik Subbarao]
* Entry.pod: fix typos [Peter Marschall]
* extend Net::LDAP::Entry->update() to take LDIF objects [Peter Marschall]
* Specify that we want to use the 'ldap' scheme to verify certificates. [Kevan Carstensen]
* Net/LDAP/Extra/AD.pm: convenience functions for AD
* various documentation updates
Notable changes in 1.2.14
- Batchlog replay can be, and is throttled by default now.
See batchlog_replay_throttle_in_kb setting in cassandra.yaml.
Notable changes in 1.2.11
- Added a new consistency level, LOCAL_ONE, that forces all CL.ONE operations
to execute only in the local datacenter.
- New replace_address to supplant the (now removed) replace_token and
replace_node workflows to replace a dead node in place. Works like the
old options, but takes the IP address of the node to be replaced.
Notable changes in 1.2.9
- A history of executed nodetool commands is now captured.
It can be found in ~/.cassandra/nodetool.history. Other tools output files
(cli and cqlsh history, .cqlshrc) are now centralized in ~/.cassandra,
as well.
- A new sstablesplit utility allows to split large sstables offline.
- After performance testing for CASSANDRA-5727, the default LCS filesize
has been changed from 5MB to 160MB.
Notable changes in 1.2.5
- Custom secondary index support has been added to CQL3. Refer to
CQL3 documentation (http://cassandra.apache.org/doc/cql3/CQL.html)
for details and examples.
Full release notes and changelogs:
https://git-wip-us.apache.org/repos/asf?p=cassandra.git;f=NEWS.txt;hb=refs/tags/cassandra-1.2.15https://git-wip-us.apache.org/repos/asf?p=cassandra.git;f=CHANGES.txt;hb=refs/tags/cassandra-1.2.15
Functionality Added or Changed
* InnoDB: New global configuration parameters, innodb_status_output and innodb_status_output_locks, allow you to dynamically enable and disable the standard InnoDB Monitor and InnoDB Lock Monitor for periodic output. Enabling and disabling monitors for periodic output by creating and dropping specially named tables is deprecated and may be removed in a future release.
* Previously, ALTER TABLE in MySQL 5.6 could alter a table such that the result had temporal columns in both 5.5 and 5.6 format. Now ALTER TABLE upgrades old temporal columns to 5.6 format for ADD COLUMN, CHANGE COLUMN, MODIFY COLUMN, ADD INDEX, and FORCE operations. This conversion cannot be done using the INPLACE algorithm, so specifying ALGORITHM=INPLACE in these cases results in an error.
* CMake now supports a -DTMPDIR=dir_name option to specify the default tmpdir value. If unspecified, the value defaults to P_tmpdir in <stdio.h>.
Bugs Fixed
* InnoDB; Replication: Using the InnoDB memcached plugin (see InnoDB Integration with memcached) with innodb_api_enable_binlog set to 1 caused the server to leak memory.
* InnoDB: A boolean mode full-text search query would result in a memory access violation during parsing.
* InnoDB: When new indexes are added by an ALTER TABLE operation, instead of only saving table-level statistics and statistics for the new indexes, InnoDB would save statistics for the entire table, including the table's other indexes. This behavior slowed ALTER TABLE performance.
* InnoDB: Due to a parser error, full-text search queries that include a sub-expression could return the wrong result.
* InnoDB: The innochecksum tool did not use a Windows-specific API to retrieve file size information, which resulted in an incorrect error message (Error: ibdata1 cannot be found) when the MySQL 5.6 innochecksum 2GB file size limit was exceeded. innochecksum now provides support for files larger than 2GB in both MySQL 5.6 and MySQL 5.7.
* InnoDB: Due to a regression introduced by the fix for Bug17371537, memory was not allocated for the default memcached engine when using the default memcached engine as the backstore for data instead of InnoDB.
* InnoDB: InnoDB would report an incorrect operating system error code after failing to initialize.
* InnoDB: Manipulating a table after discarding its tablespace using ALTER TABLE ... DISCARD TABLESPACE could result in a serious error.
* InnoDB: Persistent optimizer statistics would cause stalls due to latch contention.
* InnoDB: MATCH() ... AGAINST queries that use a long string as an argument for AGAINST() could result in an error when run on an InnoDB table with a full-text search index.
* InnoDB: An InnoDB full-text search failure would occur due to an “unended” token. The string and string length should be passed for string comparison.
* InnoDB: In debug builds, a merge insert buffer during a page read would cause a memory access violation.
* InnoDB: Truncating a memcached InnoDB table while memcached is performing DML operations would result in a serious error.
* InnoDB: In sync0rw.ic, rw_lock_x_lock_func_nowait would needlessly call os_thread_get_curr_id.
* InnoDB: Attempting to rename a table to a missing database would result in a serious error.
more...
Fix a bug (ticket 4c86b126f2) that causes rows to go missing on some queries with OR clauses and IS NOT NULL operators in the WHERE clause, when the SQLITE_ENABLE_STAT3 or SQLITE_ENABLE_STAT4 compile-time options are used.
Fix a harmless compiler warning that was causing problems for VS2013.
Release 0.1.11 (Feb 07, 2014)
-----------------------------
Bug Fixes
* Fix incorrect parsing of string literals containing line breaks (issue118).
* Fix typo in keywords, add MERGE, COLLECT keywords (issue122/124,
by Cristian Orellana).
* Improve parsing of string literals in columns.
* Fix parsing and formatting of statements containing EXCEPT keyword.
* Fix Function.get_parameters() (issue126/127, by spigwitmer).
Enhancements
* Classify DML keywords (issue116, by Victor Hahn).
* Add missing FOREACH keyword.
* Grouping of BEGIN/END blocks.
Other
* Python 2.5 isn't automatically tested anymore, neither Travis nor Tox
still support it out of the box.
MySQL Connector/C++ is a MySQL database connector for C++. It lets
you develop C++ applications that connect to the MySQL Server.
MySQL Connector/C++ offers the following benefits for C++ users
compared to the MySQL C API (MySQL client library):
* Convenience of pure C++; no C function calls required
* Supports JDBC 4.0, an industry standard API
* Supports the object-oriented programming paradigm
* Reduces development time
Changes in DBI 1.631
NOTE: This release changes the handle passed to Callbacks from being an 'inner'
handle to being an 'outer' handle. If you have code that makes use of Callbacks,
ensure that you understand what this change means and review your callback code.
Fixed err_hash handling of integer err RT#92172 [Dagfinn Ilmari]
Fixed use of \Q vs \E in t/70callbacks.t
Changed the handle passed to Callbacks from being an 'inner'
handle to being an 'outer' handle.
Improved reliability of concurrent testing
PR#8 [Peter Rabbitson]
Changed optional dependencies to "suggest"
PR#9 [Karen Etheridge]
Changed to avoid mg_get in neatsvpv during global destruction
PR#10 [Matt Phillips]
Version 3.0.0
- Major change in UTF-8 handling. If client_encoding is set to UTF-8,
always mark returned Perl strings as utf8. See the pg_enable_utf8 docs
for more information.
[Greg Sabino Mullane, David E. Wheeler, David Christensen]
- Bump DBI requirement to 1.614
- Bump Perl requirement to 5.8.1
- Add new handle attribute, switch_prepared, to control when we stop
using PQexecParams and start using PQexecPrepared. The default is 2:
in previous versions, the effective behavior was 1 (i.e. PQexecParams
was never used).
[Greg Sabino Mullane]
- Better handling of items inside of arrays, particularly bytea arrays.
[Greg Sabino Mullane] (CPAN bug #91454)
- Map SQL_CHAR back to bpchar, not char
[Greg Sabino Mullane, reported by H.Merijn Brand]
- Do not force oids to Perl ints
[Greg Sabino Mullane] (CPAN bug #85836)
- Return better sqlstate codes on fatal errors
[Rainer Weikusat]
- Better prepared statement names to avoid bug
[Spencer Sun] (CPAN bug #88827)
- Add pg_expression field to statistics_info output to show
functional index information
[Greg Sabino Mullane] (CPAN bug #76608)
- Adjust lo_import_with_oid check for 8.3
(CPAN bug #83145)
- Better handling of libpq errors to return SQLSTATE 08000
[Stephen Keller]
- Make sure CREATE TABLE .. AS SELECT returns rows in non do() cases
- Add support for AutoInactiveDestroy
[David Dick] (CPAN bug #68893)
- Fix ORDINAL_POSITION in foreign_key_info
[Dagfinn Ilmari Mannsåker] (CPAN bug #88794)
- Fix foreign_key_info with unspecified schema
[Dagfinn Ilmari Mannsåker] (CPAN bug #88787)
- Allow foreign_key_info to work when pg_expand_array is off
[Greg Sabino Mullane and Tim Bunce] (CPAN bug #51780)
- Remove math.h linking, as we no longer need it
(CPAN bug #79256)
- Spelling fixes
(CPAN bug #78168)
- Better wording for the AutoCommit docs
(CPAN bug #82536)
- Change NOTICE to DEBUG1 in t/02attribs.t test for handle attribute "PrintWarn":
implicit index creation is now quieter in Postgres.
[Erik Rijkers]
- Use correct SQL_BIGINT constant for int8
[Dagfinn Ilmari Mannsåker]
- Fix assertion when binding array columns on debug perls >= 5.16
[Dagfinn Ilmari Mannsåker]
- Adjust test to use 3 digit exponential values
[Greg Sabino Mullane] (CPAN bug #59449)
- Avoid reinstalling driver methods in threads
[Dagfinn Ilmari Mannsåker] (CPAN bug #83638)
- Make sure App::Info does not prompt for pg_config location
if AUTOMATED_TESTING or PERL_MM_USE_DEFAULT is set
[David E. Wheeler] (CPAN bug #90799)
- Fix typo in docs for pg_placeholder_dollaronly
[Bryan Carpenter] (CPAN bug #91400)
- Cleanup dangling largeobjects in tests
[Fitz Elliott] (CPAN bug #92212)
- Fix skip test counting in t/09arrays.t
[Greg Sabino Mullane] (CPAN bug #79544)
- Explicitly specify en_US for spell checking
[Dagfinn Ilmari Mannsåker] (CPAN bug #91804)
0.775 (01.18.2013) - John Siracusa <siracusa@gmail.com>
* Improved automated installation detection (RT 92254)
0.774 (11.01.2013) - John Siracusa <siracusa@gmail.com>
* Fixed typos.
0.773 (10.28.2013) - John Siracusa <siracusa@gmail.com>
* Fixed bad skip count on test file.
0.772 (10.28.2013) - John Siracusa <siracusa@gmail.com>
* Fixed a bug that caused nested arrays to be incorrectly formatted by
Rose::DB::Pg's format_array() method. (Patch by Brian Duggan.)
* Updated contributors list.
Update DEPENDS
Upstream changes:
0.08270 2014-01-30 21:54 (PST)
* Fixes
- Fix 0.08260 regression in DBD::SQLite bound int handling. Inserted
data was not affected, but any function <=> integer comparison would
have failed (originally fixed way back in 0e773352)
- Fix failure to load DateTime formatter when connecting to Firebird
over ODBC
* Misc
- All drivers based on ::Storage::DBI::Firebird::Common now return the
same sqlt_type value (affects ::DBI::Interbase, ::DBI::Firebird and
::DBI::ODBC::Firebird)
0.08260 2014-01-28 18:52 (UTC)
* New Features
- A new zero-to-DBIC style manual: DBIx::Class::Manual::QuickStart
* Notable Changes and Deprecations
- Explicitly deprecate combination of distinct and selecting a
non-column via $rs->get_column()
* Fixes
- More robust handling of circular relationship declarations by loading
foreign classes less frequently (should resolve issues like
http://lists.scsys.co.uk/pipermail/dbix-class/2013-June/011374.html)
Note that none of this is a manifestations of a DBIC bug, but rather
unexpected (but correct) behavior of load-order-dependent (hence
logically broken) Resultclass hierarchies. In order to deal with this
DBIC is scaling back a large number of sanity checks, which are to be
reintroduce pending a better framework for source registration
- Fix multiple edge cases of complex prefetch combining incorrectly
with correlated subquery selections
- Fix multiple edge cases stemming from interaction of a non-selecting
order_by specification and distinct and/or complex prefetch
- Fix unbound growth of a resultset during repeated execute/exhaust
cycles (GH#29)
- Work around (and be very vocal about the fact) when DBIC encounters
an exception object with broken string overloading
- Clarify ambiguous behavior of distinct when used with ResultSetColumn
i.e. $rs->search({}, { distinct => 1 })->get_column (...)
- Setting quote_names propagates to SQL::Translator when producing
SQLite DDL (it is one of the few producers *NOT* quoting by default)
- Fix incorrect binding of large integers on old versions of
DBD::SQLite (now DBIC simply always binds SQLite ints as BIGINT)
- Silence (harmless) warnings on recent DBD::SQLite versions, when
inserting/updating large integers on 32bit ivsize systems (RT#76395)
- Back out self-cleaning from DBIx::Class::Carp for the time being
(as a side effect fixes RT#86267)
- Fix incorrect internal use of implicit list context in copy()
- Fix 0.08250 regression in driver determination when DBI_DSN is used
- Tests no longer fail if $ENV{DBI_DSN} is set
- Throw clearer exception on ->new_related() with a non-existent
relationship
- Fix incorrect parethesis unroll with multicolumn in, (never noticed
before fixing false positive in SQLA::Test 1.77)
- Fix t/storage/replicated.t class loading problem
- Stop using the deprecated Class::MOP::load_class()
- Fix warning in t/54taint.t with explicitly unset PERL5LIB (RT#91972)
- Fix t/54taint.t failing under a local::lib with installed earlier
DBIC version (RT#92486)
* Misc
- Massive incompatible change of ::BlockRunner internals (was never
documented as usable externally, this last set of changes settles
the design for proper documentation and opening up)
- Adjust exceptions in tests to accommodate changes in the upcoming
DBD::SQLite based on libsqlite 3.8.2
- More robust lock file naming scheme - allow tests to work on exotic
MSWin32 filesystems (habitual offender being http://is.gd/iy5XVP)
- Better diagnostics when File::Spec->tmpdir gives us crap in testing
- Replace $row with $result in all docs to be consistent and to
clarify various return values
Add missing DEPENDS
Upstream changes:
revision 1.77 2014-01-17
----------------------------
- Reintroduce { -not => undef } column operator (regression from 1.75)
revision 1.75 2013-12-27
----------------------------
- *UPCOMING INCOMPATIBLE BUGFIX*: SQLA used to generate incorrect SQL
on undef-containing lists fed to -in and -not_in. An exception will
be raised for a while before properly fixing this, to avoid quiet
but subtle changes to query results in production
- Deprecate and warn when supplying an empty arrayref to like/not_like
operators (likely to be removed before 2.0)
- Warn when using an inequality operator with a multi-value array to
arrive at what amounts to a 1=1 condition (no pre-2.0 plans to fix
this behavior due to backwards comp concerns)
- Fix false negative comparison of ORDER BY <function> ASC
- More improvements of incorrect parsing (placeholder at end of list
element)
- Fix typos in POD and comments (RT#87776)
- Augment -not_bool example with nesting (RT#89601)
Added support for common table expressions and the WITH clause.
Added the printf() SQL function.
Added SQLITE_DETERMINISTIC as an optional bit in the 4th argument to the sqlite3_create_function() and related interfaces, providing applications with the ability to create new functions that can be factored out of inner loops when they have constant arguments.
Add SQLITE_READONLY_DBMOVED error code, returned at the beginning of a transaction, to indicate that the underlying database file has been renamed or moved out from under SQLite.
Allow arbitrary expressions, including function calls and subqueries, in the filename argument to ATTACH.
Allow a VALUES clause to be used anywhere a SELECT statement is valid.
Reseed the PRNG used by sqlite3_randomness(N,P) when invoked with N==0. Automatically reseed after a fork() on unix.
Enhance the spellfix1 virtual table so that it can search efficiently by rowid.
Performance enhancements.
Improvements to the comments in the VDBE byte-code display when running EXPLAIN.
Add the "%token_class" directive to LEMON parser generator and use it to simplify the grammar.
Change the LEMON source code to avoid calling C-library functions that OpenBSD considers dangerous. (Ex: sprintf).
Bug fix: In the command-line shell CSV import feature, do not end a field when an escaped double-quote occurs at the end of a CRLN line.
SQLSoup provides a convenient way to map Python objects to relational database
tables, with no declarative code of any kind. It's built on top of the
SQLAlchemy ORM and provides a super-minimalistic interface to an existing
database.
Use pypi for MASTER_SITES. From CHANGELOG:
Version 0.3 - 2014-01-31
* Add returning to Update
* Add missing params for returning
* Add columns definitions to Function
* Fix AtTimeZone mapping
Functionality Added or Changed
CMake now supports a -DTMPDIR=dir_name option to specify the default tmpdir value. If unspecified, the value defaults to P_tmpdir in <stdio.h>. Thanks to Honza Horak for the patch.
Bugs Fixed
InnoDB: Table renaming errors would appear in the LATEST FOREIGN KEY ERROR section of the SHOW ENGINE INNODB STATUS output.
Partitioning: Queries using the index_merge optimization (see Index Merge Optimization) could return invalid results when run against tables that were partitioned by HASH.
Partitioning: When no partition had returned a row since the last HA_ERR_KEY_NOT_FOUND error, the use of uninitialized memory in the priority queue used for returning rows in sorted order could lead to a crash of the server.
Replication: mysqlbinlog --verbose failed when it encountered a corrupt row event in the binary log. Such a row event could also cause the slave to fail.
Replication: When log_warnings is greater than 1, the master prints binary log dump thread information—containing the slave server ID, binary log file name, and binary log position—in mysqld.1.err. A slave server ID greater than 2 billion was printed with a negative value in such cases.
Replication: Invalid event offsets in the binary log were not always handled correctly, which could lead to replication failure.
The cache used for the Index Merge access method was freed only after successful retrieval of all rows. Interruption or failure of the operation led to a file descriptor leak.
For utf8 and utf8mb4 strings, handler functions unnecessarily called a Unicode conversion function.
Use of a nonmulti-byte algorithm for skipping leading spaces in multi-byte strings could cause a server exit.
For the utf8_bin collation, ORDER BY LOWER(col_name) could produce incorrect ordering.
On Windows, the --local-service server option did not work, and was not displayed in the --help message.
The prototype of the Performance Schema instrumentation API mysql_cond_timedwait() call was fixed to be drop-in compatible with pthread_cond_timedwait(). This fix affects only implementers of third-party plugins.
For the path specified with the --basedir option, mysql_plugin attempted to unlink the path rather than free the memory in which the path was stored.
COUNT(DISTINCT) sometimes produced an incorrect result when the last read row contained a NULL value.
Some scripts displayed out-of-date information regarding where to report bugs.
Updating a FEDERATED table with UPDATE... JOIN caused a server exit when the local table contained a single row and that row could be joined to a row in the FEDERATED table.
mysql_install_db referred to the obsolete mysqlbug script for reporting problems. It now refers to http://bugs.mysql.com/ instead.
Fixed libldap MozNSS crash
Fixed libldap memory leak with SASL
Fixed libldap assert in parse_passwdpolicy_control
Fixed libldap shortcut NULL RDNs
Fixed libldap deref to use correct control
Fixed liblmdb keysizes with mdb_update_key
Fixed slapd cn=config olcDbConfig modification
Fixed slapd-bdb/hdb to bail out of search if config is paused
Fixed slapd-bdb/hdb indexing issue with derived attributes
Fixed slapd-mdb to bail out of search if config is paused
Fixed slapd-mdb indexing issue with derived attributes
Fixed slapd-perl to bail out of search if config is paused
Fixed slapd-sql to bail out of search if config is paused
Fixed slapo-constraint handling of softadd/softdel
Fixed slapo-syncprov assert with findbase
Build Environment
Test suite: Use $(MAKE) for tests
Documentation
admin24 fix TLSDHParamFile to be correct
either because they themselves are not ready or because a
dependency isn't. This is annotated by
PYTHON_VERSIONS_INCOMPATIBLE= 33 # not yet ported as of x.y.z
or
PYTHON_VERSIONS_INCOMPATIBLE= 33 # py-foo, py-bar
respectively, please use the same style for other packages,
and check during updates.
Use versioned_dependencies.mk where applicable.
Use REPLACE_PYTHON instead of handcoded alternatives, where applicable.
Reorder Makefile sections into standard order, where applicable.
Remove PYTHON_VERSIONS_INCLUDE_3X lines since that will be default
with the next commit.
Whitespace cleanups and other nits corrected, where necessary.
v2.2.6 released 2013-12-18
* Added pt-query-digest support for Percona Server slow log rate limiting
* Added pt-agent --ping
* Added pt-mysql-summary --all-databases
* Added pt-stalk --sleep-collect
* Added pt-table-sync --[no]check-child-tables
* Fixed bug 1249150: PTDEBUG prints some info to STDOUT
* Fixed bug 1248363: pt-agent requires restart after changing MySQL options
* Fixed bug 1248778: pt-agent --install on PXC is not documented
* Fixed bug 1250973: pt-agent --install doesn't check for previous install
* Fixed bug 1250968: pt-agent --install suggest MySQL user isn't quoted
* Fixed bug 1251004: pt-agent --install error about slave is confusing
* Fixed bug 1251726: pt-agent --uninstall fails if agent is running
* Fixed bug 1248785: pt-agent docs don't list privs required for its MySQL user
* Fixed bug 1215016: pt-deadlock-logger docs use pt-fk-error-logger
* Fixed bug 1201443: pt-duplicate-key-checker error when EXPLAIN key_len=0
* Fixed bug 1217013: pt-duplicate-key-checker misses exact duplicate unique indexes
* Fixed bug 1214685: pt-mysql-summary schema dump prompt can't be disabled
* Fixed bug 1195628: pt-online-schema-change gets stuck looking for its own _new table
* Fixed bug 1249149: pt-query-digest stats prints to STDOUT instead of STDERR
* Fixed bug 1071979: pt-stak error parsing df with NFS
* Fixed bug 1223458: pt-table-sync deletes child table rows
v2.2.5 released 2013-10-16
* Added Query_time histogram bucket counts to pt-query-digest JSON output
* Added pt-online-schema-change --[no]drop-triggers option
* Fixed bug 1206677: pt-agent docs reference clodu.percona.com
* Fixed bug 1226721: pt-agent on CentOS 5 fails to send data
* Fixed bug 1199589: pt-archiver deletes data despite --dry-run
* Fixed bug 1206728: pt-deadlock-logger 2.2 requires DSN on command line
* Fixed bug 1209436: pt-kill --log-dsn may not work on Perl 5.8
* Fixed bug 1215608: pt-online-schema-change new table suffix is hard-coded
* Fixed bug 821692: pt-query-digest doesn't distill LOAD DATA correctly
* Fixed bug 984053: pt-query-digest doesn't distill INSERT/REPLACE without INTO correctly
* Fixed bug 821690: pt-query-digest doesn't distill IF EXISTS correctly
* Fixed bug 1210537: pt-table-checksum --recursion-method=cluster crashes if no nodes are found
* Fixed bug 944051: pt-table-checksum has ambiguous exit status
* Fixed bug 1229861: pt-table-sync quotes float values, can't sync
v2.2.4 released 2013-07-18
* Implemented pt-query-digest anonymous JSON output
* Implemented pt-online-schema-change timestamp output
* Fixed bug 1182856: Zero values causes "Invalid --set-vars value: var=0"
* Fixed bug 1195034: pt-deadlock-logger error: Use of uninitialized value $ts in pattern match (m//)
* Fixed bug 1137556: pt-heartbeat docs don't account for --utc
* Fixed bug 1188264: pt-online-schema-change error copying rows: Undefined subroutine &pt_online_schema_change::get
* Fixed bug 1171968: pt-query-digest docs don't mention --type=rawlog
* Fixed bug 1176010: pt-query-digest doesn't group db and `db` together
* Fixed bug 1174956: pt-query-digest and pt-fingerprint don't strip some multi-line comments
* Fixed bug 1172317: pt-sift does not work if pt-stalk did not collect due to a full disk
* Fixed bug 1136559: pt-table-checksum: Deep recursion on subroutine "SchemaIterator::_iterate_dbh"
* Fixed bug 1199591: pt-table-checksum doesn't use non-unique index with highest cardinality
* Fixed bug 1163735: pt-table-checksum fails if explicit_defaults_for_timestamp is enabled in 5.6
* Fixed bug 1168434: pt-upgrade reports differences on NULL
* Fixed bug 1168106: pt-variable-advisor has the wrong default value for innodb_max_dirty_pages_pct in 5.5 and 5.6
* Fixed bug 1168110: pt-variable-advisor shows key_buffer_size in 5.6 as unconfigured (even though it is)
v2.2.3 released 2013-06-17
* Added new tool: pt-agent
* Fixed bug 1188002: pt-online-schema-change causes "ERROR 1146 (42S02): Table 'db._t_new' doesn't exist"
v2.2.2 released 2013-04-24
* Added --show-all to pt-query-digest
* Added --recursion-method=cluster to pt-table-checksum
* Fixed bug 1127450: pt-archiver --bulk-insert may corrupt data
* Fixed bug 1163372: pt-heartbeat --utc --check always returns 0
* Fixed bug 1156901: pt-query-digest --processlist reports duplicate queries for replication thread
* Fixed bug 1160338: pt-query-digest 2.2 prints unwanted debug info on tcpdump parsing errors
* Fixed bug 1160918: pt-query-digest 2.2 prints too many string values
* Fixed bug 1156867: pt-stalk prints the wrong variable name in verbose mode when --function is used
* Fixed bug 1081733: pt-stalk plugins can't access the real --prefix
* Fixed bug 1099845: pt-table-checksum pxc same_node function incorrectly uses wsrep_sst_receive_address
* Fixed bug 821502: Some tools don't have --help or --version
* Fixed bug 947893: Some tools use @@hostname without /*!50038*/
* Fixed bug 1082406: An explicitly set wsrep_node_incoming_address may make SHOW STATUS LIKE 'wsrep_incoming_addresses' return a portless address
v2.2.1 released 2013-03-14
* Official support for MySQL 5.6
* Official support for Percona XtraDB Cluster
* Redesigned pt-query-digest
* Redesigned pt-upgrade
* Redesigned pt-fk-error-logger
* Redesigned pt-deadlock-logger
* Changed --set-vars in all tools
* Renamed --retries to --tries in pt-online-schema-change
* Added --check-read-only to pt-heartbeat
* Added MySQL options to pt-mysql-summary
* Added MySQL options to pt-stalk
* Removed --lock-wait-timeout from pt-online-schema-change (use --set-vars)
* Removed --lock-wait-timeout from pt-table-checksum (use --set-vars)
* Removed pt-query-advisor
* Removed pt-tcp-model
* Removed pt-trend
* Removed pt-log-player
* Enabled --version-check by default in all tools
* Fixed bug 1008796: Several tools don't have --database
* Fixed bug 1087319: Quoter::serialize_list() doesn't handle multiple NULL values
* Fixed bug 1086018: pt-config-diff needs to parse wsrep_provider_options
* Fixed bug 1056838: pt-fk-error-logger --run-time works differently than pt-deadlock-logger --run-time
* Fixed bug 1093016: pt-online-schema-change doesn't retry RENAME TABLE
* Fixed bug 1113301: pt-online-schema-change blocks on metadata locks
* Fixed bug 1125665: pt-stalk --no-stalk silently clobbers other options, acts magically
* Fixed bug 1019648: pt-stalk truncates InnoDB status if there are too many transactions
* Fixed bug 1087804: pt-table-checksum doesn't warn if no slaves are found
v2.1.9 released 2013-02-14
* Fixed bug 1103221: pt-heartbeat 2.1.8 doesn't use precision/sub-second timestamps
* Fixed bug 1099665: pt-heartbeat 2.1.8 reports big time drift with UTC_TIMESTAMP
* Fixed bug 1099836: pt-online-schema-change fails with "Duplicate entry" on MariaDB
* Fixed bug 1103672: pt-online-schema-change makes bad DELETE trigger if PK is re-created with new columns
* Fixed bug 1115333: pt-pmp doesn't list the origin lib for each function
* Fixed bug 823411: pt-query-digest shouldn't print "Error: none" for tcpdump
* Fixed bug 1103045: pt-query-digest fails to parse non-SQL errors
* Fixed bug 1105077: pt-table-checksum: Confusing error message with binlog_format ROW or MIXED on slave
* Fixed bug 918056: pt-table-sync false-positive error "Cannot nibble table because MySQL chose no index instead of the PRIMARY index"
* Fixed bug 1099933: pt-stalk is too verbose, fills up log
v2.1.8 released 2012-12-21
* Beta support for MySQL 5.6
* Beta support for Percona XtraDB Cluster
* pt-online-schema-change: If ran on Percona XtraDB Cluster, requires PXC 5.5.28 or newer
* pt-table-checksum: If ran on Percona XtraDB Cluster, requires PXC 5.5.28 or newer
* pt-upgrade: Added --[no]disable-query-cache
* Fixed bug 927955: Bad pod2rst transformation
* Fixed bug 898665: Bad online docs formatting for --[no]vars
* Fixed bug 1022622: pt-config-diff is case-sensitive
* Fixed bug 1007938: pt-config-diff doesn't handle end-of-line comments
* Fixed bug 917770: pt-config-diff Use of uninitialized value in substitution (s///) at line 1996
* Fixed bug 1082104: pt-deadlock-logger doesn't handle usernames with dashes
* Fixed bug 886059: pt-heartbeat handles timezones inconsistently
* Fixed bug 1086259: pt-kill --log-dsn timestamp is wrong
* Fixed bug 1015590: pt-mysql-summary doesn't handle renamed variables in Percona Server 5.5
* Fixed bug 1079341: pt-online-schema-change checks for foreign keys on MyISAM tables
* Fixed bug 823431: pt-query-advisor hangs on big queries
* Fixed bug 996069: pt-query-advisor RES.001 is incorrect
* Fixed bug 933465: pt-query-advisor false positive on RES.001
* Fixed bug 937234: pt-query-advisor issues wrong RES.001
* Fixed bug 1082599: pt-query-digest fails to parse timestamp with no query
* Fixed bug 1078838: pt-query-digest doesn't parse general log with "Connect user as user"
* Fixed bug 957442: pt-query-digest with custom --group-by throws error
* Fixed bug 887638: pt-query-digest prints negative byte offset
* Fixed bug 831525: pt-query-digest help output mangled
* Fixed bug 932614: pt-slave-restart CHANGE MASTER query causes error
* Fixed bug 1046440: pt-stalk purge_samples slows down checks
* Fixed bug 986847: pt-stalk does not report NFS iostat
* Fixed bug 1074179: pt-table-checksum doesn't ignore tables for --replicate-check-only
* Fixed bug 911385: pt-table-checksum v2 fails when --resume + --ignore-database is used
* Fixed bug 1041391: pt-table-checksum debug statement for "Chosen hash func" prints undef
* Fixed bug 1075638: pt-table-checksum Illegal division by zero at line 7950
* Fixed bug 1052475: pt-table-checksum uninitialized value in numeric lt (<) at line 8611
* Fixed bug 1078887: Tools let --set-vars clobber the required SQL mode
Changelog:
libgda 5.2.2, 2013-12-23
- Avoid using setlocale() in libraries
- Bugs corrected: GraphViz detection, #720594
- Translations:
- it (Marco Ciampa, Milo Casagrande)
libgda 5.2.1, 2013-11-17
- Fixed a Unix compilation issue, bug #712143
- Improved configure script output
- Translations:
- de (Benjamin Steinwender)
libgda 5.2.0, 2013-11-11
- Vala bindings improvements, thanks to Daniel Espinosa
- Improvements to most database providers (MySQL, PostgreSQL, SQLite, SqlCipher, JDBC, ...)
- Use SqlCipher 3.0.0 and Sqlite 3.8.0.2
- Switched to GTK+3
- Lots of work on the Windows platform
- Many bugs fixed
- Translations updated for many languages, thanks to all the translators!
15 Feb 2013
- Version 0.35
- New cdb.addmany() function for faster cdb construction
- Fix 2.5 build, needed -fPIC
- Add debian package
thx: Mike Pomraning for 10+ years of python-cdb!
Fri Sep 6 07:04:07 UTC 2013 Alexey Chebotar <alexey.chebotar@gmail.com>
* Version 0.9.16
* Fixed undefined method 'each' in LDAP::LDIF.mods_to_ldif (GH-26).
Thanks to Francesco Malvezzi.
Thu Aug 29 10:18:48 UTC 2013 Alexey Chebotar <alexey.chebotar@gmail.com>
* Version 0.9.15
* Accept nil for new_parent_dn for rename. Thanks to Kouhei Sutou.
Wed Aug 28 13:21:53 UTC 2013 Alexey Chebotar <alexey.chebotar@gmail.com>
* Version 0.9.14
* Fixed option parsing bug for LDAP::Conn.sasl_bind. Thanks to Brian Leake.
* Added possibility to use :nocanon option in rb_ldap_conn_sasl_bind.
See ldap_set_option(3) for more information. Thanks to Brian Leake.
* Added function conn.rename(dn, new_rdn, new_parent_dn, delete_old_rdn, sctrls, cctrls) => self
Modify the RDN of the entry with DN, dn, giving it the new RDN in parent new_parent_dn,
new_rdn. If delete_old_rdn is true, the old RDN value will be deleted from the entry.
Thanks to Marek Veber.
* Added option LDAP_OPT_NETWORK_TIMEOUT for openLDAP. Thanks to David Campbell.
* Fixed build error with GCC 4.8.1. Thanks to Kouhei Sutou.
* Add missing ldap_raname_s() function availability check. Thanks to Kouhei Sutou.
2013-05-15
Version 3.4.4 of Gramps! "The Ministry of Silly Names", a maintenance release.
* infinite recursion bug in narrative web generation
* protection on family trees when using version 3.4 and 4.0 on the same PC (road to 4.0)
* merging notes of media with citations now works
* crash during Calculate Preview of a filtered XML export
* fix annoying errors on navigation related to citations gramplet and tag object.
* listing the Family Trees can corrupt them.
* various fix around handling Gedcom file format
* fix citations and sources import on ProGen format
* better date handling and better alternate translation support on some textual reports according to locale under windows
* avoid Errors when setting wrong value as markup for invalid dates (Preferences)
* fix paragraph layout on PDF format or print output
* New: New-Zealand holidays
* Polish and backport code on XML import (road to 4.0)
* Regular expression rules now use search rather than match, fix design issues on regex filter rules
* Disable/Enable indent spouse on descendants tree
* fix regular expressions on Place filter rule
* consistency on cli arguments (road to 4.0)
* fix call of non-existant process on references proxy, enhanced tests on proxy filter
* fix NarWeb creation via cli for some non-english locales
* Various updated translations: ca, de, fr, it, nl, pt_BR, ru, sv, uk
Changes:
2.8.3
* [FIX] Sentinel instance role sampling fixed, the system is now more
reliable during failover and when reconfiguring instances with
non matching configuration.
* [FIX] Inline requests are now handled even when terminated with just LF.
* [FIX] Replication timeout handling greatly improved, now the slave is able
to ping the master while removing the old data from memory, and while
loading the new RDB file. This avoid false timeouts sensed by
masters.
* [FIX] Fixed a replication bug involving 32 bit instances and big datasets
hard to compress that resulted into more than 2GB of RDB file sent.
* [FIX] Return error for inline requests with unbalanced quotes.
* [FIX] Publish the slave replication offset even when disconnected from the
master if there is still a cached master instance.
2.8.2
* [FIX] Sentinel better desynchronization to avoid split-brain elections
where no Sentinel managed to get elected.
* [FIX] Stop accepting writes on "MISCONF" error only if master, not slave.
* [FIX] Reply to PING with an error on "MISCONF" errors.
2.8.1
* [FIX] Fixed a bug in "new Sentinel" config propagation.
* [FIX] Fixed a false positive in Redis tests.
2.8.0
* [FIX] Fixed an error in rdbWriteRaw() that should have no practical impact.
* [NEW] Log the new master when SLAVEOF command is used.
* [NEW] Sentinel code synchronized with the unstable branch, the new Sentinel
is a reimplementation that uses more reliable algorithms.
2.8.0 RC6
* [NEW] SCAN, SSCAN, HSCAN, ZSCAN commands.
2.8.0 RC5
* [FIX] redis-cli: don't crash with --bigkeys when the key no longer exist.
* [FIX] Allow AUTH / PING when disconnected from slave and serve-stale-data
is no.
* [FIX] PSYNC: safer handling of PSYNC requests with offsets in the future.
* [FIX] Replication: Fix master timeout detection.
* [FIX] Replication: Correctly install the write handler after successful
PSYNC.
2.8.0 RC4
* [FIX] Fixed a serious EVAL memory leak in the Lua stack.
* [FIX] Fixed server startup when no IPv6 address exists in any interface.
* [FIX] Send MISCONFIG error when BGSAVE fails because can't fork.
* [FIX] Memory efficiency with large (> a few kbytes) values improved
considerably.
* [NEW] DEBUG SDSLEN for sds memory debugging.
2.8.0 RC3
* [FIX] Improved expired keys collection algorithm. Even under heavy load keys
to be expired can't accumulate because of lack of CPU time.
* [FIX] Replication speed regression fixed (issue #1238).
* [FIX] Fixed an hard to trigger PSYNC bug.
* [FIX] Fixed Issue #1240, ZUNIONSTORE could lead to wrong result.
* [NEW] Add per-db average TTL information in INFO output.
* [NEW] redis-benchmark improvements.
* [NEW] dict.c API wrong usage detection.
2.8.0 RC2
* [FIX] Fixed a critical replication bug, see issue #1221.
* [NEW] The new inline protocol now accepts quoted strings like, for example
you can now type in a telnet session: set 'foo bar' "hello world\n".
2.8.0 RC1
* [NEW] Slaves are now able to partially resynchronize with the master,
so most of the times a full resynchronization with the RDB creation
in the master side is not needed when the master-slave link is
disconnected for a short amount of time.
* [NEW] Experimental IPv6 support.
* [NEW] Slaves explicitly ping masters now, a master is able to detect
a timed out slave independently.
* [NEW] Masters can stop accepting writes if not enough slaves with a given
maximum latency are connected.
* [NEW] Keyspace changes notifications via Pub/Sub.
* [NEW] CONFIG SET maxclients is now available.
* [NEW] Ability to bind multiple IP addresses.
* [NEW] Set process names so that you can recognize, in the "ps" command
output, the listening port of an instance, or if it is a saving child.
* [NEW] Automatic memory check on crash.
* [NEW] CONFIG REWRITE is able to materialize the changes in the configuration
operated using CONFIG SET into the redis.conf file.
* [NEW] More NetBSD friendly code base.
* [NEW] PUBSUB command for Pub/Sub introspection capabilities.
* [NEW] EVALSHA can now be replicated as such, without requiring to be
expanded to a full EVAL for the replication link.
* [NEW] Better Lua scripts error reporting.
* [NEW] SDIFF performance improved.
* [FIX] A number of bugfixes.
2.6.17
* [FIX] redis-cli: fix big keys search when the key no longer exist.
* [FIX] Allow AUTH / PING when disconnected from slave with serve-stale-data
on.
* [FIX] redis-benchmark: update help for new __rand_int__ form.
* [FIX] Fix broken rdbWriteRaw() return value check in rdb.c (harmless).
* [FIX] Log to what master a slave is going to connect to.
* [FIX] Only run the fast active expire cycle if master & enabled.
* [FIX] Fixed a replication bug involving 32 bit instances and big datasets
hard to compress that resulted into more than 2GB of RDB file sent.
Changes since 1.4.0:
- COUCHDB-1781: The official documentation has been overhauled.
- New administration UI, included as an experimental preview.
- COUCHDB-1888: Fixed an issue where admin users would be restricted
by the public_fields feature.
- Fixed an issue with the JavaScript CLI test runner.
- COUCHDB-1867: An experimental plugin feature has been added.
- COUCHDB-1894: An experimental Node.js-based query server runtime added.
- COUCHDB-1901: Better retry mechanism for transferring attachments during
replication.
Fixes to the UPDATE FUNCTIONS for upgrades from releases earlier than 2.2.0
Fixes to the FAILOVER logic
Fixes slon to avoid constant database connection & disconnection
Fixes to CLONE PREPARE processing
(update dependency from py-amkCrypto to py-crypto).
0.7.1 - 2009-11-16
New features:
- Entities can now be declared "abstract" so that they do not create a table,
etc... This allows, among others, an entity to inherit from multiple abstract
classes (patch from Stephane Klein, closes#89).
- Added a new collection which can resolve entities relative to the current
entity, for example "..other_module.Class" (based on patches from Johannes
Janssen, closes#93).
- Added a new entity option "resolve_root", which allows one to specify the
root module where your entities are defined. The string will be prepended
to all "absolute" entity paths. It can also be used on a per-entity basis.
This feature is based on a patch from Johannes Janssen, see #93.
Changes:
- using_options_defaults and using_table_options statements can be used several
times within the same class (closes#70).
Bug fixes:
- Fixed custom base classes and versioned extension when used with zope
interfaces (closes#98, patch from Valentin Lab)
- Fixed having relationships in custom base classes (based on patch
by Stephane Klein)
Upstream changes:
1.68 Mon Aug 6 22:22:22 PDT 2012
Patch fromFileGetTopLines() and fromFileIsHeader(), which are used by fromFile(). Impact: minor.
Improve performance of fromFileGuessOS()
Improve fromFile(), fromCSV(), csv() to support using \r, \n within a CSV field.
join() now supports {matchNULL => 1, NULLasEmpty => 1}, if one would like to treat NULL as empty string, or
treat NULL as equal (however, not equal to empty string). Both are set to 0 by default.
Suggested by Kyle Horton & Wilson Dave.
Remove inheritance from AutoLoader and Exporter.
Thanks to Brian Wightman
Thanks to Nicholas Andonakis for sharing his code, quite a few ideas in his package inspired the improvements below!
Add new shortcut methods: lastRow(), lastCol(), colName($colNumericIndex)
One can now write
foreach my $i (0..$t->lastRow)
instead of
foreach my $i (0..$t->nofRow-1)
Add iterator(), so that one can now write
my $next = $t_product->iterator();
while (my $row = $next->()) {
# have access to a row as a hash reference, access row number by &$next(1);
$t_product->setElm($next->(1), 'ProductName', 'New! '.$row->{ProductName});
}
addCol() can take the default value for the new column (first argument)
addRow() supports {addNewCol => 1}
moveCol() can take a $newColName.
setElm() can set a value for multiple cells, specified by ref to row array and col array
match_string(), match_pattern(), match_pattern_hash() also produce $parentTable->{MATCH}
# match returns all matched row ids in $t_product->{MATCH} (ref to row ID array)
$t_product->match_pattern_hash('$_{UnitPrice} > 20');
# create a new column, with 'No' as the default value
$t_product->addCol('No', 'IsExpensive');
# use $t_product->{MATCH} to set values for multiple Elements
$t_product->setElm($t_product->{MATCH}, 'IsExpensive', 'Yes');
1.67 Wed Jul 25 11:47:23 PDT 2012
Update Change.txt file to point out $keepRestCol defaults to 1 is only for group()
For pivot(), $keepRestCol is still default to 0 as before.
1.66 Wed Jul 25 11:03:29 PDT 2012
Change the default value of keepRestCol in group() to 1, instead of 0 to be compatible with older versions
Thanks to Kyle Horton
6.0.1:
* Clarification of license. Thanks to
Jan Staněk <jstanek@redhat.com> for bringing this issue up.
This work is now explicitly licensed under 3-clause BSD license.
* Fixed a long standing bug (August 2008, rev 9fd52748fa59)
on "dbtables.py". Notified by Maxime Labelle.
* If you want to link with Oracle Berkeley DB 6.0, you will
need to create the environment variable
'YES_I_HAVE_THE_RIGHT_TO_USE_THIS_BERKELEY_DB_VERSION'
to signal to the pybsddb that you are legal. To be legal,
your code MUST be AGPL3 *OR* you have to buy a commercial
license from Oracle.
If you are not legally entitled to use Berkeley DB 6.0 and
you have previous versions of Berkeley DB on your system,
you can a) delete Berkeley DB 6.0 and try again, OR
b) instruct pybsddb to use a previous Berkeley DB version,
using environment variables or command line options.
Sorry for the inconvenience. I am trying to protect you.
Some details:
https://forums.oracle.com/message/11184885http://lists.debian.org/debian-legal/2013/07/
The replication issue affects some users of PostgreSQL binary replication, and can cause minor data loss between the master and the standby. While not all users are affected, it is difficult to predict when the bug will occur, so we urge all users of replication and continuous backup (PITR) to update immediately. Additionally, users who had replication running under PostgreSQL minor versions 9.3.0, 9.3.1, 9.2.5, 9.1.10, or 9.0.14 should plan to take a fresh base backup of each standby after update, in order to ensure no prior data corruption already exists.
This release also fixes two timing issues with VACUUM, which can cause old, overwritten or deleted rows to re-appear at a later date under some circumstances. Users with very high transaction rates, particularly those who experience "transaction ID wraparound" every few weeks or less, are the most at risk for this issue. Those users should set vacuum_freeze_table_age to 0, and run a database-wide VACUUM after the update. The second of the two VACUUM issues affects only 9.3, making it expecially important for 9.3 users to update.
=== 4.5.0 (2013-12-02)
* Support :on_commit=>(:drop|:delete_rows|:preserve_rows) options when creating temp tables on PostgreSQL (rosenfeld) (#737)
* Make Dataset#insert work on PostgreSQL if the table name is a SQL::PlaceholderLiteralString (jeremyevans) (#736)
* Copy unique constraints when emulating alter_table operations on SQLite (jeremyevans) (#735)
* Don't return clob column values as SQL::Blob instances in the db2 and ibmdb adapters unless use_clob_as_blob is true (jeremyevans)
* Make use_clob_as_blob false by default on DB2 (jeremyevans)
* Fix usage of Sequel::SQL::Blob objects as prepared statement arguments in jdbc/db2 adapter when use_clob_as_blob is false (jeremyevans)
* Add mssql_optimistic_locking plugin, using a timestamp/rowversion column to protect against concurrent updates (pinx, jeremyevans) (#731)
* Make Model.primary_key array immutable for composite keys (chanks) (#730)
=== 4.4.0 (2013-11-01)
* Make Database#tables not show tables in the recycle bin on Oracle (jeremyevans) (#728)
* Don't automatically order on all columns when emulating offsets for unordered datasets on DB2 (jeremyevans)
* Improve PostgreSQL type support in the jdbc/postgresql adapter (jeremyevans)
* Make offset emulation on Oracle work when using columns that can't be ordered (jeremyevans, sdeming) (#724, #725)
* Make filter by associations support handle associations with :conditions or block (jeremyevans)
* Make association cloning handle :block correctly for clones of clones (jeremyevans)
* Make association cloning handle :eager_block option correctly (jeremyevans)
* Make add_primary_key work on h2 (jeremyevans)
* Add support for foreign key parsing on Oracle (jeremyevans)
* Add support for foreign key parsing to the jdbc adapter (jeremyevans)
* Make add_foreign_key work on HSQLDB (jeremyevans)
* Add table_select plugin for selecting table.* instead of * for model datasets (jeremyevans)
* Issue constraint_validation table deletes before inserts, so modifying constraint via drop/add in same alter_table block works (jeremyevans)
* Support add_*/remove_*/remove_all_* pg_array_to_many association methods on unsaved model objects (jeremyevans)
* Add Sybase SQLAnywhere support via new sqlanywhere and jdbc/sqlanywhere adapters (gditrick, jeremyevans)
* Add Dataset#offset for setting the offset separately from the limit (Paul Henry, jeremyevans) (#717)
=== 4.3.0 (2013-10-02)
* Fix literalization of empty blobs on MySQL (jeremyevans) (#715)
* Ensure Dataset#page_count in pagination extension is at least one
(jeremyevans) (#714)
* Recognize another disconnect error in the jdbc/as400 adapter (jeremyevans)
* Make Dataset#qualify and Sequel.delay work together (jeremyevans)
* Recognize citext type as string on PostgreSQL (isc) (#710)
* Support composite keys in the rcte_tree plugin (jeremyevans)
* Support composite keys in the tree plugin (jeremyevans)
* Make Migrator.migrator_class public (robertjpayne, jeremyevans) (#708)
* Make PostgreSQL empty array literalization work correctly on PostgreSQL <8.4
(jeremyevans)
* Add Sequel extensions guide (jeremyevans)
* Add model plugins guide (jeremyevans)
* Add error_sql Database extension, allowing DatabaseError#sql to return SQL
query that caused underlying exception (jeremyevans)
* Make Dataset#each_page in pagination extension return enumerator if no block
is given (justinj) (#702)
== v0.17.0 [2013-09-15] Michael Granger <ged@FaerieMUD.org>
Bugfixes:
- Fix crash by calling PQsend* and PQisBusy without GVL (#171).
Enhancements:
- Add method PG::Connection#copy_data.
- Add a Gemfile to allow installation of dependencies with bundler.
- Add compatibility with rake-compiler-dev-box.
- Return self from PG::Result#check instead of nil. This allows
to stack method calls.
Changed the defined behavior for the CAST expression when floating point values greater than +9223372036854775807 are cast into into integers so that the result is the largest possible integer, +9223372036854775807, instead of the smallest possible integer, -9223372036854775808. After this change, CAST(9223372036854775809.0 as INT) yields +9223372036854775807 instead of -9223372036854775808. ← Potentially Incompatible Change!
Added support for WITHOUT ROWID tables.
Added the skip-scan optimization to the query planner.
Extended the virtual table interface, and in particular the sqlite3_index_info object to allow a virtual table to report its estimate on the number of rows that will be returned by a query.
Update the R-Tree extension to make use of the enhanced virtual table interface.
Add the SQLITE_ENABLE_EXPLAIN_COMMENTS compile-time option.
Enhanced the comments that are inserted into EXPLAIN output when the SQLITE_ENABLE_EXPLAIN_COMMENTS compile-time option is enabled.
Performance enhancements in the VDBE, especially to the OP_Column opcode.
Factor constant subexpressions in inner loops out to the initialization code in prepared statements.
Enhanced the ".explain" output formatting of the command-line shell so that loops are indented to better show the structure of the program.
Enhanced the ".timer" feature of the command-line shell so that it shows wall-clock time in addition to system and user times.
fixed since version 4.0.9:
- bug #4150 Clicking database name in query window opens a new tab
- bug #4141 Wrong page is shown after editing; also, do not show a modal
dialog for multi-row edit
- bug #3939 PHP NavigationTree error when paging through list
- bug #4075 Support A10 Networks load balancer
- bug #4083 row deleting isn't binlogs friendly
- bug #4163 Setup script does not recognize manually-configured server
- bug #4158 Events page says no privileges with ALL PRIVILEGES
FoxPro, Clipper, xBase) files. It can also be used to create DBF files and
populate them from your data. It is written for the Linux/Unix environment,
but relies only on standard C libraries and functions.
* Previously, MySQL Server distributions included the MySQL Reference Manual in Info format (the Docs/mysql.info file). Because the license for the manual restricts redistribution, its inclusion in Community packages caused problems for downstream redistributors, such as those who create Linux distributions. Community distributions of MySQL Server no longer include the mysql.info file, to make the repackaging and redistribution process easier (for example, the source tarball and its checksum can be used directly). This change applies to all source and binary Community packaging formats. Commercial (Enterprise) distributions are unchanged.
* Incompatible Change: Several statement instruments in the setup_instruments table are used by the Performance Schema during the early stages of statement classification before the exact statement type is known.
* The Performance Schema now instruments the read/write lock Delegate::lock
* A new CMake option, WITH_ASAN, permits enabling address sanitization for compilers that support it.
* The hash function used for metadata locking was modified to reduce overhead.
* Bugs Fixed
* Previously, MySQL Server distributions included the MySQL Reference Manual in Info format (the Docs/mysql.info file). Because the license for the manual restricts redistribution, its inclusion in Community packages caused problems for downstream redistributors, such as those who create Linux distributions. Community distributions of MySQL Server no longer include the mysql.info file, to make the repackaging and redistribution process easier (for example, the source tarball and its checksum can be used directly). This change applies to all source and binary Community packaging formats. Commercial (Enterprise) distributions are unchanged.
* A new CMake option, WITH_ASAN, permits enabling address sanitization for compilers that support it.
* Attempts to use the thread_concurrency system variable (which has an effect only for Solaris 8 and earlier) now indicate that it has no effect when that is the case.
* Bugs Fixed
I have no idea why the extended regexp does not catch the unsetenv declaration
but the check is redundant anyway (there is another unsetenv check below in
configure) so I don't care that much.
The build does not create all those unnecessary shlib symlinks on MirBSD
(I believe this is due to a patch I sent in years ago), so add separate
PLIST.MirBSD files that do not contain these files.
(BTW, I would be grateful to learn how I can achieve the same effect
without copying PLISTs, but this works.)
Fixed liblmdb nordahead flag
Fixed liblmdb to check cursor index before cursor_del
Fixed liblmdb wasted space on split
Fixed slapd for certs with a NULL issuerDN
Fixed slapd cn=config with empty nested includes
Fixed slapd syncrepl memory leak with delta-sync MMR
Fixed slapd-bdb/hdb to stop processing on dn not found
Fixed slapd-bdb/hdb with indexed ANDed filters
Fixed slapd-mdb to stop processing on dn not found
Fixed slapd-mdb dangling reader
Fixed slapd-mdb matching rule for OlcDbEnvFlags
Fixed slapd-mdb with indexed ANDed filters
Fixed slapd-meta from blocking other threads
Fixed slapo-syncprov assert with findbase
The following bugs were fixed since the release of version 4.0.8:
- bug #4104 Can't edit updatable view when searching
- bug #4108 Missing refresh by deleting databases
- bug #3995 Drizzle server charset notice
- bug #3911 Filtering database names includes empty groupings
- bug #3678 Does not display or manipulate bit(64) fields appropriately
- bug #4129 Unneeded navi panel refresh
- bug #4120 SSL redirects to port 80
- bug #4144 DROP DATABASE displays wrong database name
- bug #4059 Running delete query asks for confirmation but says it was
already executed
- bug #4147 Accessibility: Images without Alt nor title attribute
Release 0.1.10 (Nov 02, 2013)
-----------------------------
Bug Fixes
* Removed buffered reading again, it obviously causes wrong parsing in some rare
cases (issue114).
* Fix regression in setup.py introduced 10 months ago (issue115).
Enhancements
* Improved support for JOINs, by Alexander Beedie.
Upstream changes:
Fixed err for new drh to be undef not to 0 [Martin J. Evans]
Fixed RT#83132 - moved DBIstcf* constants to util
export tag [Martin J. Evans]
PrintWarn is now triggered by warnings recorded in methods like STORE
that don't clear err RT#89015 [Tim Bunce]
Changed tracing to no longer show quote and quote_identifier calls
at trace level 1.
Changed DBD::Gofer ping while disconnected set_err from warn to info.
Clarified wording of log message when err is cleared.
Changed bootstrap to use $XS_VERSION RT#89618 [Andreas Koenig]
Added connect_cached.connected Callback P R # 3 [David E. Wheeler]
Clarified effect of refs in connect_cached attributes [David E. Wheeler]
Extended ReadOnly attribute docs for when the driver cannot
ensure read only [Martin J. Evans]
Corrected SQL_BIGINT docs to say ODBC value is used P R # 5 [ilmari]
Added liblmdb nordahead environment flag
Fixed client tools CLDAP with IPv6
Fixed libldap CLDAP with IPv6
Fixed libldap lock ordering with abandon op
Fixed liblmdb segfault with mdb_cursor_del
Fixed liblmdb when converting to writemap
Fixed liblmdb assert on MDB_NEXT with delete
Fixed liblmdb wasted space on split
Fixed slapd cn=config with olcTLSProtocolMin
Fixed slapd-bdb/hdb optimize index updates
Fixed slapd-ldap chaining with cn=config
Fixed slapd-ldap chaning with controls
Fixed slapd-mdb optimize index updates
Fixed slapd-meta chaining with cn=config
Fixed slapo-constraint to no-op on nonexistent entries
Fixed slapo-dds assert on startup
Fixed slapo-memberof to not replicate internal ops
Fixed slapo-refint to not replicate internal ops
Build Environment
Fixed slapd-mdb ptr arithmetic on void *s
Documentation
ldapsearch(1) minor typo fix
slapd-passwd(5) minor typo fix
Changes since 1.4.46:
* tcadb.cc (tcadbmisc): compilation warnings ware supressed.
* tchdb.cc (tchdbfbpmerge): size checking was added.
* tcbdb.cc (tcbdbrangeimpl): a bug of dead locking was fixed.
6.0.0:
* Support Berkeley DB 6.0.x.
* HEADS UP: If you are using "bsddb3._bsddb" in your code,
for example for exceptions, change it to "bsddb3._db".
* Print test working directory when running the testsuite.
You can control it using "TMPDIR" environment variable.
Defaults to "/tmp/z-Berkeley_DB/".
* Support for "DB_EVENT_REP_AUTOTAKEOVER_FAILED" event.
* Support for "DB_REPMGR_ISVIEW", "DB_DBT_BLOB", "DB_LOG_BLOB",
"DB_STREAM_READ", "DB_STREAM_WRITE" and "DB_STREAM_SYNC_WRITE" flags.
* Some DB_SEQUENCE function signatures changed in Berkeley DB 6.0.x.
* Erratic behaviour of "DBEnv->rep_elect()" because a typo.
* The testsuite prints Python bitness (32/64).
* Tests compatible with hash randomization, default
in Python 3.3. See http://bugs.python.org/issue13703 .
* Errors when trying to calculate the length of a DB were
masked, and an unuseful and unrelated exception was raised.
* Code cleanup since pybsddb is not in the Python 3.x stdlib
anymore, and the version in Python 2.6/2.7 is being
maintained separately.
* Improvements to documentation generation.
Release 0.1.9 (Sep 28, 2013)
----------------------------
Bug Fixes
* Fix an regression introduced in 0.1.5 where sqlparse didn't properly
distinguished between single and double quoted strings when tagging
identifier (issue111).
Enhancements
* New option to truncate long string literals when formatting.
* Scientific numbers are pares correctly (issue107).
* Support for arithmetic expressions (issue109, issue106; by prudhvi).
Added the unlikely() and likelihood() SQL functions to be used as hints to the query planner.
Enhancements to the query planner:
Take into account the fact WHERE clause terms that cannot be used with indices still probably reduce the number of output rows.
Estimate the sizes of table and index rows and use the smallest applicable B-Tree for full scans and "count(*)" operations.
Added the soft_heap_limit pragma.
Added support for SQLITE_ENABLE_STAT4
Added support for "sz=NNN" parameters at the end of sqlite_stat1.stat fields used to specify the average length in bytes for table and index rows.
Avoid running foreign-key constraint checks on an UPDATE if none of the modified columns are associated with foreign keys.
Added the SQLITE_MINIMUM_FILE_DESCRIPTOR compile-time option
Added the win32-longpath VFS on windows, permitting filenames up to 32K characters in length.
The Date And Time Functions are enhanced so that the current time (ex: julianday('now')) is always the same for multiple function invocations within the same sqlite3_step() call.
Add the "totype.c" extension, implementing the tointeger() and toreal() SQL functions.
FTS4 queries are better able to make use of docid<$limit constraints to limit the amount of I/O required.
Added the hidden fts4aux languageid column to the fts4aux virtual table.
The VACUUM command packs the database about 1% tighter.
The sqlite3_analyzer utility program is updated to provide better descriptions and to compute a more accurate estimate for "Non-sequential pages"
Refactor the implementation of PRAGMA statements to improve parsing performance.
The directory used to hold temporary files on unix can now be set using the SQLITE_TMPDIR environment variable, which takes precedence over the TMPDIR environment variable. The sqlite3_temp_directory global variable still has higher precedence than both environment variables, however.
Added the PRAGMA stats statement.
Bug fix: Return the correct answer for "SELECT count(*) FROM table" even if there is a partial index on the table.
## Rails 3.2.15 (Oct 16, 2013) ##
* When calling the method .find_or_initialize_by_* from a collection_proxy it
should set the inverse_of relation even when the entry was found on the db.
*arthurnn*
* Callbacks on has_many should access the in memory parent if a inverse_of is
set.
*arthurnn*
* Fix `FinderMethods#last` unscoped primary key.
Fixes#11917.
*Eugene Kalenkovich*
* Load fixtures from linked folders.
*Kassio Borges*
* When using optimistic locking, `update` was not passing the column to
`quote_value` to allow the connection adapter to properly determine how to
quote the value. This was affecting certain databases that use specific
colmn types.
Fixes: #6763
*Alfred Wong*
pax -rw, the destination directory must exist. pax in NetBSD creates it if
not, pax in MirBSD complains. I read through all pkgsrc Makefiles that use
pax and added an entry to INSTALLATION_DIRS, or an INSTALL_DATA_DIR
invocation.
I did not test all the changes but they should be fairly safe. If you notice
any breakage because of this change, please contact me.
Changes since 0.7.10:
- Compatibility for Python 2.4 is being dropped.
- The primaryjoin argument is no longer needed when constructing a
relationship() against a class that has multiple foreign key paths to the
target.
- Relationships against self-referential, composite foreign keys where a
column points to itself are now supported.
- Previously difficult custom join conditions, like those involving
functions and/or CASTing of types, will now function as expected in most
cases.
- New Class/Object Inspection System.
- A new enhancement to the aliased() construct has been added called
with_polymorphic() which allows any entity to be “aliased” into a
“polymorphic” version of itself, freely usable anywhere.
- The PropComparator.of_type() method can now be used to target any number
of target subtypes, by combining it with the new with_polymorphic()
function.
- Mapper and instance events can now be associated with an unmapped
superclass, where those events will be propagated to subclasses as those
subclasses are mapped. The propagate=True flag should be used.
- The registry of class names is now sensitive to the owning module and
package of a given class. The classes can be referred to via dotted name
in expressions.
- The “deferred reflection” feature allows the construction of declarative
mapped classes with only placeholder Table metadata, until a prepare()
step is called, given an Engine with which to reflect fully all tables
and establish actual mappings. The system supports overriding of columns,
single and joined inheritance, as well as distinct bases-per-engine.
- A new SQL registration system allows a mapped class to be accepted as a
FROM clause within the core.
- The new UPDATE..FROM mechanics work in query.update().
- Upon rollback(), only those objects that were made dirty since the last
flush will be expired, the rest of the Session remains intact.
- Caching Example now uses dogpile.cache.
- The new operator system in Core associates new and overridden operators
with types.
- SQL expressions can now be associated with types.
- The inspect() function introduced in New Class/Object Inspection System
also applies to the core.
- select() now has a method Select.correlate_except() which specifies
“correlate on all FROM clauses except those specified”.
- Support for Postgresql’s HSTORE type is now available as
postgresql.HSTORE. This type makes great usage of the new operator system
to provide a full range of operators for HSTORE types, including index
access, concatenation, and containment methods such as has_key(),
has_any(), and matrix().
- The postgresql.ARRAY type will accept an optional “dimension” argument,
pinning it to a fixed number of dimensions and greatly improving
efficiency when retrieving results.
- SQLite has no built-in DATE, TIME, or DATETIME types, and instead
provides some support for storage of date and time values either as
strings or integers.
- The “collate” keyword, long accepted by the MySQL dialect, is now
established on all String types and will render on any backend, including
when features such as MetaData.create_all() and cast() is used.
- Geared towards MySQL, a “prefix” can be rendered within any of these
constructs.
- The consideration of a “pending” object as an “orphan” has been made more
aggressive.
- The after_attach event fires after the item is associated with the
Session instead of before; before_attach added.
- Query now auto-correlates like a select() does.
- Correlation is now always context-specific.
- create_all() and drop_all() will now honor an empty list as such.
- Repaired the Event Targeting of InstrumentationEvents.
- No more magic coercion of “=” to IN when comparing to subquery in
MS-SQL.
- The Session.is_modified() method accepts an argument passive which
basically should not be necessary, the argument in all cases should be
the value True - when left at its default of False it would have the
effect of hitting the database, and often triggering autoflush which
would itself change the results. In 0.8 the passive argument will have no
effect, and unloaded attributes will never be checked for history since
by definition there can be no pending state change on an unloaded
attribute.
- Column.key is honored in the Select.c attribute of select() with
Select.apply_labels().
- A relationship() that is many-to-one or many-to-many and specifies
“cascade=’all, delete-orphan’”, which is an awkward but nonetheless
supported use case (with restrictions) will now raise an error if the
relationship does not specify the single_parent=True option.
- Adding the inspector argument to the column_reflect event.
- The MySQL dialect does two calls, one very expensive, to load all
possible collations from the database as well as information on casing,
the first time an Engine connects. Neither of these collections are used
for any SQLAlchemy functions, so these calls will be changed to no longer
be emitted automatically. Applications that might have relied on these
collections being present on engine.dialect will need to call upon
_detect_collations() and _detect_casing() directly.
- Inspector.get_primary_keys() is deprecated, use
Inspector.get_pk_constraint.
- Case-insensitive result row names will be disabled in most cases. It will
be available only optionally, by passing the flag `case_sensitive=False`
to `create_engine()`, but otherwise column names requested from the row
must match as far as casing.
- The sqlalchemy.orm.interfaces.InstrumentationManager class is moved to
sqlalchemy.ext.instrumentation.InstrumentationManager.
- SQLSoup is now moved into its own project and documented/released
separately; see https://bitbucket.org/zzzeek/sqlsoup.
- The older “mutable” system within the SQLAlchemy ORM has been removed.
- We had left in an alias sqlalchemy.exceptions to attempt to make it
slightly easier for some very old libraries that hadn’t yet been upgraded
to use sqlalchemy.exc. Some users are still being confused by it however
so in 0.8 we’re taking it out entirely to eliminate any of that confusion.
From the release announcement:
This is a bug fix release which includes the following fixes:
* Allow the dump of pg schemas [Guillaume Lelarge]]
* Prevent a crash on Windows when dropping a column or a constraint on
a table [Dhiraj Chawla]
* Ensure DDLScript will work with Slony 2.2+ which has a new SQL level
API [Neel Patel]
* Fix ordering of object types in the display options and add Event
Triggers which were missing [Dhiraj Chawla].
* Ensure the debugger can cope with functions that have an OUT
parameter as the first. [Ashesh Vashi]
* Fix the quoting of user mapping objects [Dinesh Kumar]
* Ensure that materialised views are available as targets for synonyms
[Neel Patel]
* Fix the query used to find tables in a Slony replication set [Neel Patel]
* Prevent a crash if a user starts an external process such as a
backup, and then immediately hits cancel [Neel Patel].
* Fix a memory leak in the Event Trigger code [Dinesh Kumar].
For more information or to download, please visit the website at
http://www.pgadmin.org/.
Guarantee transmission of all WAL files before replica failover
Prevent downcasing of non-ASCII identifiers
Fix several minor memory leaks
Correct overcommit behavior when using more than 24GB of work memory
Improve planner cost estimates for choosing generic plans
Fix estimates of NULL rows in boolean columns
Make UNION ALL and inheritance query plans recheck parameterized paths
Correct pg_dump bugs for foreign tables, views, and extensions
Prevent a parallel pg_restore failure on certain indexes
Make REINDEX revalidate constraints
Prevent two deadlock issues in SP-GIST and REINDEX CONCURRENTLY
Prevent GiST index lookup crash
Fix several regular expression failures
Allow ALTER DEFAULT PRIVILEGES to work on all schemas
Loosen restrictions on keywords
Allow various spellings of infinity
Expand ability to compare rows to records and arrays
Prevent psql client crash on bad PSQLRC file
Add spinlock support for ARM64
Guarantee transmission of all WAL files before replica failover
Prevent downcasing of non-ASCII identifiers
Fix several minor memory leaks
Correct overcommit behavior when using more than 24GB of work memory
Improve planner cost estimates for choosing generic plans
Fix estimates of NULL rows in boolean columns
Make UNION ALL and inheritance query plans recheck parameterized paths
Correct pg_dump bugs for foreign tables, views, and extensions
Prevent a parallel pg_restore failure on certain indexes
Make REINDEX revalidate constraints
Prevent two deadlock issues in SP-GIST and REINDEX CONCURRENTLY
Prevent GiST index lookup crash
Fix several regular expression failures
Allow ALTER DEFAULT PRIVILEGES to work on all schemas
Loosen restrictions on keywords
Allow various spellings of infinity
Expand ability to compare rows to records and arrays
Prevent psql client crash on bad PSQLRC file
Add spinlock support for ARM64
The following bugs were fixed since the release of version 4.0.7:
- bug #3988 Rename view is not working
- bug #4041 Interaction between linkified fields and grid editing
- bug #3975 Table grouping isn't implemented properly
- bug #4060 Browser tries to remember wrong password when creating new user
- bug #4002 Edit Index on big table doesn't show "Loading" or any message
- bug #4098 Default table tab is ignored
- bug #4099 Server/library difference warning: setting is ignored
- bug #4100 table tree group strategy
- bug #4102 ALTER TABLE ORDER BY and InnoDB
- bug #4103 Tracking report: cannot delete a statement
- bug #3996 Drizzle navigation doesn't expand
- bug #4074 GIS column editor: point not displayed
- bug #4109 Drizzle tables in navigation are shown as views
- bug #4095 NUL symbols added to the end of database dump file
- bug #4105 More disappears in table Structure
- bug #3992 Multi-row edit doesn't clear values when checking NULL
shared-mime-info 1.2 (2013-09-30)
* Mime-type changes:
- Use IANA registered application/sql type for SQL
- Add test for text/x-python
- Added *.pyx as Pyrex/Cython variant of text/x-python
- Lower the priority of the *png glob on Apple PNGs
- Add magic for Kobo e-book reader
- Add another magic for EPub books
- Add missing globs and tests for OpenPGP files
- Add MIME types for raw disk images
- Add video/x-matroska-3d mime-type
- Use application/vnd.adobe.flash.movie for SWF
- Use application/vnd.nintendo.snes.rom for SNES ROMs, associate *.sfc with them
- Fix shebang matches for shell scripts
- Remove *.ogv as a glob for Theora videos as they might not be Theora
- Improve detection of Perl scripts
- Add more aliases for Photoshop images
- Add Microsoft Publisher mime-type
- Correct JPEG2000 definition
* Check for errors when saving files, and ensure that files
are saved to disk before carrying on.
* Don't use access() to check for writability
* Rename configure.in to configure.ac
HSQLDB (HyperSQL DataBase) is the leading SQL relational database
engine written in Java. It offers a small, fast multithreaded and
transactional database engine with in-memory and disk-based tables
and supports embedded and server modes.
This package contains library file (hsqldb.jar) only, and it is
old and should be used only for LibreOffice package.
* InnoDB: The row_sel_sec_rec_is_for_clust_rec function would incorrectly prepare to compare a NULL column prefix in a secondary index with a non-NULL column in a clustered index.
* InnoDB: An incorrect purge would occur when rolling back an update to a delete-marked record.
* InnoDB: InnoDB would rename a user-defined foreign key constraint containing the string “_ibfk_” in its name, resulting in a duplicate constraint.
* InnoDB: Rolling back an INSERT after a failed BLOB write would result in an assertion failure. The assertion has been modified to allow NULL BLOB pointers if an error occurs during a BLOB write.
* InnoDB: The srv_master_thread background thread, which monitors server activity and performs activities such as page flushing when the server is inactive or in a shutdown state, runs on a one second delay loop. srv_master_thread would fail to check if the server is in a shutdown state before sleeping.
* InnoDB: An infinite loop could occur in buf_page_get_gen when handling compressed-only pages.
* Within a stored program, comparison of the value of a scalar subquery with an IN clause resulted in an error for the first execution and raised an assertion for the second execution.
* The my_strtoll10() function could incorrectly convert some long string-format numbers to numeric values and fail to set the overflow flag.
* For queries that accessed an INFORMATION_SCHEMA table in a subquery, and attempt to lock a mutex that had already been locked could cause a server crash.
* For DIV expressions, assignment of the result to multiple variables could cause a server crash.
* mysqldump wrote SET statements as SET OPTION, which failed when reloaded because the deprecated OPTION keyword has been removed from SET syntax.
* If one connection changed its default database and simultaneously another connection executed SHOW PROCESSLIST, the second connection could access invalid memory when attempting to display the first connection's default database. memory.
* MySQL 5.7 changed audit log file output to a new format that has better compatibility with Oracle Audit Vault. This format has been backported to MySQL 5.6 and it is possible to select either the old or new format using the new audit_log_format system variable, which has permitted values of OLD and NEW (default OLD). For details about each format, see The Audit Log File.
* Important Change; Replication: START SLAVE UNTIL SQL_AFTER_GTIDS did not cause the slave to stop until the next GTID event was received following execution of the transaction having the indicated GTID, which could cause issues in the case when the next GTID event is delayed, or does not exist. Now the slave stops after completing the transaction with that GTID.
* InnoDB; Partitioning: Following any query on the INFORMATION_SCHEMA.PARTITIONS table, InnoDB index statistics as shown in the output of statements such as SELECT * FROM INFORMATION_SCHEMA.STATISTICS were read from the last partition, instead of from the partition containing the greatest number of rows.
* InnoDB: When logging the delete-marking of a record during online ALTER TABLE...ADD PRIMARY KEY, InnoDB writes the transaction ID to the log as it was before the deletion or delete-marking of the record. When doing this, InnoDB would overwrite the DB_TRX_ID field in the original table, which could result in locking issues.
* InnoDB: The row_sel_sec_rec_is_for_clust_rec function would incorrectly prepare to compare a NULL column prefix in a secondary index with a non-NULL column in a clustered index.
* InnoDB: An incorrect purge would occur when rolling back an update to a delete-marked record.
* InnoDB: An assertion would be raised in fil_node_open_file due to a missing .ibd file. Instead of asserting, InnoDB should return false and the caller of fil_node_open_file should handle the return message.
* InnoDB: The assertion ut_ad(oldest_lsn <= cur_lsn) in file buf0flu.cc would fail because the current max LSN would be retrieved from the buffer pool before the oldest LSN.
* InnoDB: InnoDB memcached add and set operations would perform more slowly than SQL INSERT operations.
* InnoDB: The InnoDB memcached plugin could be initialized to insert into an InnoDB table with an INTEGER primary key.
More...
