Right, but that is not the reason why timestamps dont use TIMESTAMP. You can always create the column without auto update functionality, according to mysql's website. You must always have a default value for a timestamp, so that might be a reason why it's not used, but that doesnt seem like a big enough reason, IMO.
AFAIK, there is no reason why Rails must use DATETIME over TIMESTAMP except for the range of dates supported. Does anyone have a reason for why Rails uses DATETIME over TIMESTAMP for timestamp fields? I ran some tests and it looks like they behave the same within Rails. Aryk Hassan Schroeder wrote: > On Fri, Oct 31, 2008 at 10:48 AM, Aryk Grosz > <[EMAIL PROTECTED]> wrote: >> >> I haven't seen anywhere in the mysql documentation that TIMESTAMP data >> type will automatically update itself. > > <http://dev.mysql.com/doc/refman/5.0/en/timestamp.html> > > -- > Hassan Schroeder ------------------------ [EMAIL PROTECTED] -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
