#31622: Support CREATE CONSTRAINT TRIGGER constraints in postgres.
-------------------------------------+-------------------------------------
Reporter: Jerome Leclanche | Owner: (none)
Type: New feature | Status: closed
Component: contrib.postgres | Version: 3.1
Severity: Normal | Resolution: wontfix
Keywords: constraints, | Triage Stage:
postgres, triggers | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jerome Leclanche):
Here's a butchered version of the code which pulls in actual postgres
functions used as constraints. The functions are versioned in migrations.
https://gist.github.com/jleclanche/07961a08b7741cb804b1f14177d19a1f
It's primitive, doesn't support updating (has to drop+recreate), and it
hacks into `constraints = []` so that it's picked up by the migration
auto-detector. But hey, it works. And incidentally it made me realize
there is no way to add new operations to be auto-detected by the migration
engine.
--
Ticket URL: <https://code.djangoproject.com/ticket/31622#comment:5>
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/068.af3cedaa3c9351efc2f62734c44409bd%40djangoproject.com.
