#25879: Uncertainty about constraint checks during fixture loading
-------------------------------+--------------------
Reporter: pakal | Owner: nobody
Type: Bug | Status: new
Component: Documentation | Version: 1.9
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------
I've encountered this paragraph in docs :
{{{
https://docs.djangoproject.com/en/1.9/ref/django-admin/#what-s-a-fixture
Note that the order in which fixture files are processed is undefined.
However, all fixture data is installed as a single transaction, so data in
one fixture can reference data in another fixture. If the database backend
supports row-level constraints, these constraints will be checked at the
end of the transaction.
}}}
However, from my experience, heavily used DBs like MySQL do not have
deferred constraint checking :
http://stackoverflow.com/a/5014744/345876
So if fixtures are loaded in undefined ordered, tehse references might
trigger referential integrity errors on these DB engines.
Are there things I'm missing here, or shouldn't we add a note on this ?
--
Ticket URL: <https://code.djangoproject.com/ticket/25879>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/048.fab75f8568b7f2b6afa1d08e40009a2f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
