Michael Koziarski wrote: >> 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.
Hmm. That doesn't negate the ability to at least conduct searches based on what the db can contain, but it's a valid point in that it makes implementing full support for it difficult. OK, well, that settles that. I'll drop it. >From an app code perspective, one way around this inability is to use varchar for dates (in the ISO format). I've done that before too in a few cases where a variety pf reasons made using varchars for dates easier to work with (casting on demand when needed for calculations). It's nice to not have to do that, but it works. Anyway, thanks for listening. -- gw -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
