> 2. TIMESTAMP requires a default value, hence interfering with the > magic > timestamp logic from Rails. This is NOT TRUE either. In my tests, > Rails > populates the created_at/created_on field the same way as it would for > DATETIME, since it ignores the default timestamp value assigned to it > from the TIMESTAMP data type.
What if I have a "published_at" field? If you force that to be a TIMESTAMP (since I'm assuming your arguing that a migration with t.datetime should turn into a MySQL TIMESTAMP) then all of my records will have some value in published_at when the non-published ones should have a null value. Would that be a reason not to do it? It's late and I haven't thought it all the way through :) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
