#3156: [patch] [multidb] datetime with auto_now=True causes integrity error
-----------------------------------+----------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: new | Component: Database wrapper
Version: other branch | Resolution:
Keywords: | Stage: Ready for checkin
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-----------------------------------+----------------------------------------
Comment (by [EMAIL PROTECTED]):
Replying to [ticket:3156 [EMAIL PROTECTED]:
> When adding a new object with a DateTimeField(auto_now=True) an
Integrity error is thrown because a NULL value is about to be inserted in
a not null column. This is because the pre_save method of the
DateTimeField incorrectly calls the superclass of DateTime instead of its
own superclass. Patch provided.
I think you mean "DateField", not "DateTime". Thanks for the patch.
--
Ticket URL: <http://code.djangoproject.net/ticket/3156#comment:2>
Django Code <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 [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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
