#25879: Uncertainty about constraint checks during fixture loading
-------------------------------+--------------------------------------
Reporter: pakal | Owner: nobody
Type: Bug | Status: new
Component: Documentation | Version: 1.9
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by pakal):
Hum to me these tickets are more complementary than duplicates, mine was
just a doc update, the #15578 seems to deal with an engine that has no
"deferred constraint checking" (although i'm not sure that this feature
would suffice to solve the OP's problem) but proposes changes in the
behaviour of loaddata instead.
Should I bring my notes to the other ticket, so that both aspects (docs &
behaviour) get matched whatever the choices made ?
--
Ticket URL: <https://code.djangoproject.com/ticket/25879#comment:2>
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/063.fb0980ef181f1cf9b0c754e3a6771663%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
