#13818: Check Child IDs before creating parent IDs
---------------------------------------------------+------------------------
Reporter: pizzapanther | Owner: nobody
Status: closed | Milestone:
Component: Database layer (models, ORM) | Version: 1.2
Resolution: invalid | Keywords: sprintdec10
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by tttallis):
* status: new => closed
* needs_better_patch: => 0
* needs_tests: => 0
* keywords: => sprintdec10
* needs_docs: => 0
* resolution: => invalid
Comment:
There's not enough detail here to reproduce the problem IMHO. We simply
don't know what state the dB was in when this error occurred. Specifically
we don't know how "the auto incremented parent id was already used in the
child table". If this state was created via the ORM, then there is a
genuine problem, but we'd need to know how you managed to do that before
moving forward.
I'm also not convinced that the stacktrace is complaining about the pk
being already in use. You may find some clues in #3997 "Missing default
value causes exception on save"
--
Ticket URL: <http://code.djangoproject.com/ticket/13818#comment:1>
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 [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.
