Hey Robert, Thanks for the response. Yeah, I didn't bring up the range / date limitations for timestamp because that's pretty well understood and documented. That is, after all, the reason why it takes up half the space in the database.
At this point, my conclusion on this whole topic is. Whenever you have a timestamp field that you know will never have values before the year 1970, than you can use: "add column created_at TIMESTAMP NULL DEFAULT NULL" instead of datetime without any problems. Does anyone see anything wrong with this? -- 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 -~----------~----~----~----~------~----~------~--~---
