MySQL-4.0.15

[highos@…]

I plan on getting this done inside of a week, just wanted to claim it in advance.

[iwanek@…]

new version

[highos@…]

Now in CVS.

[highos@…]

Version increment.

[highos@…]

Version increment (3.23.53);

o Small fix in safe_mysqld for some shells. o Fixed that SHOW STATUS doesn't reset Delayed_insert_threads. o Fixed core dump bug when using the BINARY cast on a NULL value. o Fixed race condition when someone did a GRANT at the same time a new user

logged in or did a USE DATABASE.

o Fixed bug in ALTER TABLE and RENAME TABLE when running with -O

lower_case_table_names=1 (typically on windows) when giving the table name in uppercase.

o Fixed that -O lower_case_table_names=1 also converts database names to

lower case.

o Fixed unlikely core dump with SELECT ... ORDER BY ... LIMIT.

Changed AND/OR to report that they can return NULL. This fixes a bug in GROUP BY on AND/OR expressions that return NULL.

o Fixed a bug that OPTIMIZE of locked and modified MyISAM table, reported

table corruption.

o Fixed a BDB-related ALTER TABLE bug with dropping a column and shutting

down immediately thereafter.

o Fixed problem with configure ... --localstatedir=.... o Fixed problem with UNSIGNED BIGINT on AIX (again). o Fixed bug in pthread_mutex_trylock() on HPUX 11.0. o Multithreaded stress tests for InnoDB.

[billyoc@…]

Version increment.

[highos@…]

Version increment (3.23.54a)

[billyoc@…]

Version increment. This is a bugfix release for the current stable tree. Users who use MySQL in an untrusted multi-user environment should consider upgrading to this version, which also fixes a bug that enabled valid local users to crash mysqld by using a specially modified mysql client application.

[highos@…]

Version increment (3.23.56)

​http://www.mysql.com/doc/en/News-3.23.56.html

[mattrogers@…]

this was dubbed "production" on the 25th. perhaps it's time for an update? :)

[highos@…]

Yeah, but who the hell is using 4.x right now? And how compatible is it with 3.23.*? I don't want to upgrade the version and have a large amount of software that depend on mysql break. Would be a major pita.

Perhaps it would be better to include two versions of MySQL in the blfs-book- even if the commands are similar. (or just a note saying, use the same instructions as the older version, just use the newer package or what not.)

Dunno.. discuss ;)

[highos@…]

Version increment (4.0.13);

Nobody has commented on the usage of 4.0.x yet, eh? Oh well :P

[igor@…]

I haven't noticed that any BLFS package depends on MySQL3 so there is no need to keep it in the book.

[igor@…]

Version increment (4.0.15)

[(none)]

Milestone post-1.0 deleted