auto_increment fields get mangled in some cases when doing an alter table

* from blah; ++---+---+ | id | stuff | morestuff | ++---+---+ | 2 | blah | 0 | ++---+---+ 1 row in set (0.00 sec) -- tani hosokawa river styx internet - Before posting

timezones aren't being properly handled

variables' even though the system timezone is set to EST. This bug is known to affect Redhat 7.2 and Redhat 7.1. -- tani hosokawa river styx internet - Before posting, please check: http://www.mysql.com/manual.php

broken error log message

: `xx' (Got error %d from table handler) -- tani hosokawa river styx internet - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request

replication involving now() is sketchy if the two server clocks differ.

or may not have the same kind of data. Replicated data should not use now() but should instead have the value calculated by now(). Fix: Submitter-Id: submitter ID Originator: Organization: tani hosokawa river styx internet MySQL support: email support Synopsis: now() shouldn't

the ORDER BY bug fix in 3.23.35

According to the changelog, there's a bug in ORDER BY that was recently introduced but fixed in 3.23.35. 3.23.34 fixed a bug in bidirectional replication though, so I'm wondering what the specifics of the bugs were, since I want to do bidirectional replication, but don't want a serious ORDER BY