> I would argue this is not an issue of "most" or even "standard" -- most > code on the planet is probably written with camelCase names -- which > doesn't seem to have much impact on Rails' opinion.
The real problem is that you *can't* retrieve that data again. Rails needs to coerce those values into a Date or Time, neither of which accept 0000-00-00. So we can't support it when reading data, there's not much point letting you write it. After all, you can't construct the time object to save in the first place. Given that ruby can't support that value, coercing to nil seems at least reasonable. > This is a simple case of having the database adaptor allow what the > database itself considers legal. Not only legal, but Rails is preventing > the db from using its own default behavior. It doesn't matter if the > DB2, Oracle or Sybase worlds think its dumb. Its an adaptor for MySQL. > > -- gw > -- > Posted via http://www.ruby-forum.com/. > > > > -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core?hl=en -~----------~----~----~----~------~----~------~--~---
