#31440: Add a standard way to set deferrable constraints.
-------------------------------------+-------------------------------------
Reporter: Ian Foote | Owner: Ian Foote
Type: New feature | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: constraints | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by felixxm):
* status: assigned => closed
* resolution: => wontfix
Comment:
Thanks for this ticket, however you don't need to use a `SET CONSTRAINTS`
statements in most of transactions, usage is so niche that IMO it's
acceptable to force users to call `cursor.execute('SET CONSTRAINTS ...')`
if they really need to. It's just not worth to maintain this hook. You can
of course start a discussion on DevelopersMailingList if you don't agree.
--
Ticket URL: <https://code.djangoproject.com/ticket/31440#comment:4>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.2ab49f6f1e24ae124d028d203cf1ceca%40djangoproject.com.
