On Dec 15, 2006, at 12:17 PM, Adrian Holovaty wrote:
> I'd suggest using a CharField instead. The downside to this is that > you can't take advantage of date-specific queries, such as retrieving > all the records where the date is in a certain month, but whether > that's a problem depends on your application. Thanks Adrian, I guess if Postgres were to accept an out of range date like 1972-00-00 it would sort of defeat the date manipulation mechanism. :-) I think what I'll do in my case, since I'd eventually like to use the date info for building timelines, is to consider a null day value the first of the month. That way I can be accurate to the month. If I don't know the month, I don't know the date. That should work for most of the recordings I'm dealing with. To be moral about it, I guess I could also put a column in the db to flag the approximation. Thanks again for your hard work. I'm an 'upgrader' from Cakephp and I couldn't be more impressed. I'm also a Jayhawk! Lived in Lawrence for 20+ years, now in New York. Regards Dan J. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
