#12753: Fixture loading can fails on second syncdb when auto_now_add field is
ommitted
-------------------------------------+-------------------------------------
Reporter: russellm | Owner:
Type: Bug | dmedvinsky
Component: Core | Status: new
(Serialization) | Version:
Severity: Release blocker | 1.4-beta-1
Keywords: | Resolution:
Has patch: 1 | Triage Stage: Accepted
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by ptone):
From discussion at the sprints with Karen, Paul and jezdez, the consensus
was that this was in fact fixed by r16739, as Russ implies in the original
mail thread that the fact that the fixture loading the first time was a
bug.
I've attached a draft release note about this backwards incompatibility.
--
Ticket URL: <https://code.djangoproject.com/ticket/12753#comment:17>
Django <https://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-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
