On Nov 24, 2007 10:45 PM, Greg Willits <[EMAIL PROTECTED]> wrote: > If a (MySQL) database table declares a datetime field as NOT NULL with a > default value of 0000-00-00 00:00:00 and an empty value is submitted to > that field via Rails, Rails complains that the field cannot be null. If > a string literal of 0000-00-00 00:00:00 is submitted, Rails coerces the > value to nil, and once again complains about not null. >
This is the biggest issue for me - the coercion. How "agnostic" is Rails attempting to be if it's actively overriding or erroring on what the selected DB allows for values? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
