| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
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/
|
|
ocaml-findlib/buildlink3.mk does.
|
|
|
|
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.
|
|
ocaml-findlib/buildlink3.mk does.
|
|
rc.d script overrides my.cnf directives. Hardcoding the PID can cause a
problem on systems transitioning to MySQL packages from pkgsrc.
|
|
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)
|
|
Add a one-character fix for a problem that might cause incorrect query results on a query that mixes DISTINCT, GROUP BY in a subquery, and ORDER BY.
|
|
|
|
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.
|
|
Fix a potential buffer overread that could result when trying to search a corrupt database file.
|
|
recovery in version 9.3, as well as several other minor issues in all versions. All users of version 9.3 are urged to update their installations at the next possible downtime. Users of older versions should update at their convenience.
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.
|
|
|
|
|
|
Exact changes nor release note isn't available but several bug fixes and
better support for Ruby 2.1. For more information, please refer commit
log <https://github.com/brianmario/mysql2/commits/master>.
|
|
|
|
Moneta provides a standard interface for interacting with various kinds of
key/value stores. Moneta supports the well-known NoSQL and document based
stores.
|
|
Changes from 1.2.1 to 1.3.2 are too many to write here, please refer
<https://github.com/puppetlabs/hiera/commits/master>.
|
