Straight from the docs for the latest version, regarding the initialization and updating of timestamp columns (emphasis their's, snarky parentheticals mine):
It goes on like that, with a number of curious statements which make me wonder if the developers sat in a back room drinking cheap whiskey and making up "features" to foist on people.
The second bullet point is scary. Why the hell would I want to have "DEFAULT NULL" treated as "DEFAULT CURRENT_TIMESTAMP"? I want my database to do what I tell my database to do, damn it. What's worse, they refer to the first timestamp column. Ignoring the fact that the MySQL is drifting even further from the relational model (sets aren't ordered!), there's a very practical issue here. If I drop and recreate a table, my table's behavior can change dramatically if I reorder my columns. That should not be relevant.
And for other timestamp columns, DEFAULT NULL is treated as DEFAULT 0? Why? This doesn't make a damned bit of sense to me. It also worries me given Adrian's post on a similar MySQL issue.
Reading through the comments for those docs is also "real fun".
MySQL: Transactions, check. Triggers, check. Foreign keys, check. Still a toy? Check.
Why the hell would I want to have "DEFAULT NULL" treated as "DEFAULT CURRENT_TIMESTAMP"?
Because I certainly don't believe that all of my middleware has the exact same time, and I want a single canonical reference for the time I added a row to the database.
Maybe I'm too lazy always to include now() every time I insert a row into the table, and I'm definitely too lazy to write a stored procedure to insert the row or a trigger to set those values, but the fewer magical things the middleware has to do and the more magical things the database can do consistently, I consider a good thing.
Re:When? now()!
clscott on 2007-04-20T20:52:39
I can't say you've provided a convincing argument for why a DEFAULT NULL gets current timestamp or 0 depending on it's position.
If the the designer has said they want an empty timestamp to default to NULL, the value should be NULL, not whatever the database decides to do with it.
What if my first timestamp column in a table represents the date that I shipped an order to a customer and the second represents the date it was ordered? If I haven't shipped it to the customer yet... ? That's one heck of an odd implementation detail to work around. Yes, it is documented but it doesn't Do What I Told it Too which is more important than Do What I Mean.
Re:When? now()!
chromatic on 2007-04-21T01:58:53
I can't say you've provided a convincing argument for why a DEFAULT NULL gets current timestamp or 0 depending on it's position.True. Likewise, I didn't provide a convincing argument why butterscotch is disgusting, but at least I can defend that position.
Re:When? now()!
Aristotle on 2007-04-20T21:04:41
Yes, that is a good argument showing that it makes perfect sense to use
DEFAULT CURRENT_TIMESTAMP.However, am I missing something, or did you fail to even notice that the point in question is about
DEFAULT NULL(which is being treated the same asDEFAULT CURRENT_TIMESTAMPfor some bizarre reason (except when it’s not))?Re:When? now()!
chromatic on 2007-04-21T01:58:09
However, am I missing something, or did you fail to even notice that the point in question is aboutDEFAULT NULL...You're right; I did fail to notice that. Somehow I turned it around in my head so that it meant "When you insert no value into this column," which is completely different.
