On 11/27/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Julio Nobrega wrote: > > I don't think it Django should work/accept Mysql's 0000-00-00. The > > correct data you need is NULL. > > In my experience i've seen the date '0000-00-00' used as a "min date" > (which is not NULL). I'm not advocating this use, but i've seen it > done. A NULL date is not the same, semantically, as the earliest > possible date. It's a subtle distinction but i've seen applications > that depend on it.
Ok... but I think it's strange... The earliest possible "positive" date is 01-01-0000, isn't? 0000-00-00 is wrong, and these developers coded around a bug. Anyway, Adrian said Django will handle this old Mysql behaviour... -- Julio Nobrega - http://www.inerciasensorial.com.br --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
