> http://dev.mysql.com/doc/mysql/en/timestamp-4-1.html > > > Absolutely brilliant document *g* ... > > > > So now, it makes a difference if it's the first TIMESTAMP column, > > if it's running in MaxDB mode, if it has a defaulf of NULL (which will > > be silently changed), if it has no default, a default of > > CURRENT_TIMESTAMP, or it matters if there's an ON UPDATE > > clause... > > And it depends on which *minor* release it is. 4.1.0 is different from > 4.1.1 is different from 4.1.2 is different from 4.1.3 is different > from 4.1.6. And it depends on how long ago you sacrificed a goat and > the position og te moon. >
Changing functionality and adding columns etc in minor point releases is something I really hate about MySQL. Same for removing or changing column names from system commands. Truely annoying. Never heard of "backwards compatibility" I guess... Had a conversation with some MySQL folks - really hard to get the point through to them... > > Damn man... The guy who thought this up should be smacked in the head! > > Should be made to fix it :) No, smacked in the head... :-) With regards, Martijn Tonies Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL Server Upscene Productions http://www.upscene.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
