#3615: Can't define forward references in fixtures using MySQL with InnoDB
-------------------------------------+-------------------------------------
Reporter: russellm | Owner: nobody
Type: Bug | Status: new
Milestone: | Component: Database layer
Version: SVN | (models, ORM)
Resolution: | Severity: Normal
Triage Stage: Accepted | Keywords: mysql innodb myisam
Needs documentation: 0 | reference fixture
Patch needs improvement: 1 | Has patch: 1
UI/UX: 0 | Needs tests: 0
| Easy pickings: 0
-------------------------------------+-------------------------------------
Comment (by anonymous):
Replying to [comment:21 jsdalton]:
> It looks like this ticket has a patch that's almost there. The primary
issue is the patch opens the possibility of inserting rows with bad
referential integrity while foreign_key_checks is disabled. Presumably, if
we could find a solution to this problem, the remaining issues Russel
identifies here https://code.djangoproject.com/ticket/3615#comment:8 could
be addressed.
Recreating the indexes will also perform the checks - the main problem
with that approach is that it's slow, which makes it complicated for
testing but not so bad for most normal uses. Based on testing in my fork
(above) it seems like the best answer might just be finding the right way
to sequence it so you could do most of the work with foreign_key_checks
off and simply recreate the indexes once when all of the fixture loading
is complete.
Chris
--
Ticket URL: <https://code.djangoproject.com/ticket/3615#comment:22>
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.
