Thanks for your reponse guys! It is a production machine with a lot of custom software, so I cannot change that right now. For me, it worked fine under Django 1.0.3 alpha and postgres 8.2.7 ! ??
Wim On 9 jun, 13:43, David De La Harpe Golden <david.delaharpe.gol...@ichec.ie> wrote: > On 09/06/10 12:23, Wim Feijen wrote: > > > Hello, > > > Do you know whether there is a minimum to a date? > > Well there is, at the postgresql level, dates are supported > between 4713 BC and 5874897 AD > > http://www.postgresql.org/docs/8.4/static/datatype-datetime.html > > Maybe there's some text to date parser level stuff going funny, but > FWIW, I can set a 21 Jan 61 date with django 1.1.2 and postgresql 8.4 > > d = datetime(61,01,21) > s = SomeModel.objects.all()[0] > s.some_timestamp_field = d > s.save() > > > I'm using Django 1.0.5 alpha > > That's quite an old django version at this stage I guess, > I wonder if it's doing the same db connection init. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
