Voor de volledigheid ook nog de niet onbelangrijke changelog van 3.23.50, die nooit officieel is uitgebracht. Vooral InnoDB heeft in .50 belangrijke wijzigingen ondergaan, zoals volwaardige support voor foreign key constraints.
<img src=g/nblt.gif width=6 height=9> MySQL 3.23.50 changelog:
[li]Fixed problem with `crash-me' and gcc 3.0.4.
[li]Fixed that `@@unknown_variable' doesn't hang server.
[li]Added `@@VERSION' as a synonym for `VERSION()'.
[li]`SHOW VARIABLES LIKE 'xxx'' is now case insensitive.
[li]Fixed timeout for `GET_LOCK()' on HPUX with DCE threads.
[li]Fixed memory allocation bug in the glibc library used to build
Linux binaries, which caused mysqld to die in 'free()'.
[li]Fixed `SIGINT' and `SIGQUIT' problems in `mysql'.
[li]Fixed bug in character table converts when used with big ( > 64K)
[li]`InnoDB' now retains foreign key constraints through `ALTER TABLE'
and `CREATE/DROP INDEX'.
[li]`InnoDB' now allows foreign key constraints to be added through the
`ALTER TABLE' syntax.
[li]`InnoDB' tables can now be set to automatically grow in size
[li]Fixed some buffer overflow problems when reading startup
[li]Because of problems on shutdown we have now disabled named pipes on
windows by default. One can enable named pipes by starting mysqld
[li]Fixed bug when using `WHERE key_column = 'J' or key_column='j''.
[li]Fixed core-dump bug when using `--log-bin' with `LOAD DATA INFILE'
without an active database.
[li]Fixed bug in `RENAME TABLE' when used with
`lower_case_table_names=1' (default on Windows).
[li]Fixed unlikely core-dump bug when using `DROP TABLE' on a table
that was in use by a thread that also used queries on only
[li]Fixed problem with `SHOW CREATE TABLE' and `PRIMARY KEY' when using
[li]Fixed that one can use `SET PASSWORD' for the anonymous user.
[li]Fixed core-dump bug when reading client groups from option files
[li]Memory leak (16 bytes per every *corrupted* table) closed.
[li]Fixed binary builds to use `--enable-local-infile'.
[li]Update source to work with new `bison' version.
[li]Updated shell scripts to new agree with new POSIX standard.
[li]Fixed bug where `DATE_FORMAT()' returned empty string when used
with `GROUP BY'.[/list]
<img src=g/nblt.gif width=6 height=9> InnoDB 3.23.50 changelog:
[li]InnoDB now supports an auto-extending last data file. You do not need to preallocate the whole data file at the database startup.
[li]Made several changes to facilitate the use of the InnoDB Hot Backup tool. It is a separate non-free tool you can use to take online backups of your database without shutting down the server or setting any locks.
[li]If you want to run the InnoDB Hot Backup tool on an auto-extending data file you have to upgrade it to version ibbackup-0.35.
[li]The log scan phase in crash recovery will now run much faster.
[li]Starting from this server version, the hot backup tool truncates unused ends in the backup InnoDB data files.
[li]To allow the hot backup tool to work, on Windows we no longer use unbuffered i/o or native async i/o; instead we use the same simulated async i/o as on Unix.
[li]You can now define the ON DELETE CASCADE or ON DELETE SET NULL clause on foreign keys.
[li]FOREIGN KEY constraints now survive ALTER TABLE and CREATE INDEX.
[li]We suppress the FOREIGN KEY check if any of the column values in the foreign key or referenced key to be checked is the SQL NULL. This is compatible with Oracle, for example.
[li]SHOW CREATE TABLE now lists also foreign key constraints. Also mysqldump no longer forgets about foreign keys in table definitions.
[li]You can now add a new foreign key constraint with ALTER TABLE ... ADD CONSTRAINT FOREIGN KEY (...) REFERENCES ... (...).
[li]FOREIGN KEY definitions now allow backquotes around table and column names.
[li]MySQL command SET TRANSACTION ISOLATION LEVEL ... has now the following effect on InnoDB tables: if a transaction is defined as SERIALIZABLE then InnoDB conceptually adds LOCK IN SHARE MODE to all consistent reads. If a transaction is defined to have any other isolation level, then InnoDB obeys its default locking strategy which is REPEATABLE READ.
[li]SHOW TABLE STATUS no longer sets an x-lock at the end of an auto-increment index if the auto-increment counter has already been initialized. This removes in almost all cases the surprising deadlocks caused by SHOW TABLE STATUS.
[li]Fixed a bug: in a CREATE TABLE statement the string 'foreign' followed by a non-space character confused the FOREIGN KEY parser and caused table creation to fail with errno 150. [/list]