#11984: Problem with date_hierarchy in Django 1.1 - Truncated incorrect datetime
value: '0000-01-01 00:00:00'
-------------------------------------------------+--------------------------
Reporter: sergey.g.ales...@gmail.com | Owner: sorin
Status: assigned | Milestone:
Component: django.contrib.admin | Version: 1.1
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------------------+--------------------------
Comment (by sorin):
First, rememeber that Django is not always used to connect to new
databases so changing the values from the database is not always an
option. I'm sure other people have legacy databases that are using the
0000-00-00 format instead of NULL for dates. This is something accepted by
MySQL and should be accepted by Django also.
Also I don't think that this patch does have a negative impact on any
other back-ends - in fact all it does is that it does detect possible
errors in order to prevent application crash.
--
Ticket URL: <http://code.djangoproject.com/ticket/11984#comment:9>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=.
