A date field should contain only valid dates or be null. If you need a third alternative, use a code/switch field or store your date in a string. I don't believe there are any valid scenarios where storing invalid dates in a date field is more appropriate than using a separate code/switch to indicate the additional context.
On Nov 24, 2007, at 10:45 PM, Greg Willits wrote: ... snipped parts of prior included posts > > Well, NULL is for that third alternative. As it stands, Rails allows > only two states for dates. A valid date or NULL. There are occassions, > rare as they may be, to interpret date data in three ways just like > numerics or strings. > > -- gw > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
