Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • 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

    • 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 as DEFAULT CURRENT_TIMESTAMP for some bizarre reason (except when it’s not))?

      • However, am I missing something, or did you fail to even notice that the point in question is about DEFAULT 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.