#1584: [patch] auto_now_add fields set to NULL on update
------------------------------------------------+---------------------------
Reporter: Andy Dustman <[EMAIL PROTECTED]> | Owner: adrian
Type: defect | Status: new
Priority: normal | Milestone: Version 0.92
Component: Database wrapper | Version: SVN
Severity: normal | Resolution:
Keywords: |
------------------------------------------------+---------------------------
Comment (by [EMAIL PROTECTED]):
This is biting me as well on trunk. Using a a !FileField in conjunction.
The patch does not seem to work for me though. Although someone on IRC did
solve his problem with it. Leaves me to assume the issue runs a bit
deeper.
I see that after a save in the Admin gui the failing SQL is an UPDATE with
the date field set to None on the update, which of course fails the
constraint and gives me an !IntegrityError submit_date may not be NULL.
submit_date is: models.DateField(auto_now_add = True)
--
Ticket URL: <http://code.djangoproject.com/ticket/1584>
Django <http://code.djangoproject.org/>
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-updates@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-updates
-~----------~----~----~----~------~----~------~--~---
