Alterações na distribuição 3.23.34 (10 Mar 2001)

Added the INNOBASE storage engine and the BDB storage engine to the MariaDB source distribution.

• Updated the documentation about GEMINI tables.
• Fixed a bug in INSERT DELAYED that caused threads to hang when inserting NULL into an AUTO_INCREMENT column.
• Fixed a bug in CHECK TABLE / REPAIR TABLE that could cause a thread to hang.
• REPLACE will not replace a row that conflicts with an AUTO_INCREMENT generated key.
• mysqld now only sets CLIENT_TRANSACTIONS in mysql->server_capabilities if the server supports a transaction-safe storage engine.
• Fixed LOAD DATA INFILE to allow numeric values to be read into ENUM and SET columns.
• Improved error diagnostic for slave thread exit.
• Fixed bug in ALTER TABLE ... ORDER BY.
• Added max_user_connections variable to mysqld.
• Limit query length for replication by max_allowed_packet, not the arbitrary limit of 4 MB.
• Allow space around = in argument to --set-variable.
• Fixed problem in automatic repair that could leave some threads in state Waiting for table.
• SHOW CREATE TABLE now displays the UNION=() for MERGE tables.
• ALTER TABLE now remembers the old UNION=() definition.
• Fixed bug when replicating timestamps.
• Fixed bug in bidirectional replication.
• Fixed bug in the BDB storage engine that occurred when using an index on multi-part key where a key part may be NULL.
• Fixed MAX() optimization on sub-key for BDB tables.
• Fixed problem where garbage results were returned when using BDB tables and BLOB or TEXT fields when joining many tables.
• Fixed a problem with BDB tables and TEXT columns.
• Fixed bug when using a BLOB key where a const row wasn't found.
• Fixed that mysqlbinlog writes the timestamp value for each query. This ensures that one gets same values for date functions like NOW() when using mysqlbinlog to pipe the queries to another server.
• Allow --skip-gemini, --skip-bdb, and --skip-innodb options to be specified when invoking mysqld, even if these storage engines are not compiled in to mysqld.
• One can now do GROUP BY ... DESC.
• Fixed a deadlock in the SET code, when one ran SET @foo=bar, where bar is a column reference, an error was not properly generated.

Retornar