#30849: Enabling hooking into the autodetector from a third-party app.
-------------------------------------+-------------------------------------
Reporter: Emil 'Skeen' Madsen | Owner: Emil
| 'Skeen' Madsen
Type: New feature | Status: closed
Component: Migrations | Version: 2.2
Severity: Normal | Resolution: wontfix
Keywords: automigrator | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* status: assigned => closed
* resolution: => wontfix
Comment:
Hello Emil, thanks for posting to the mailing list before submitting a new
feature request.
I can't say this feature wouldn't be useful for other purposes but your
`Meta.constraint_triggers` motivation could likely be implemented with the
[https://docs.djangoproject.com/en/2.2/ref/models/constraints/ new
constraints API] by subclassing `Constraint` to return custom SQL for
trigger/function creation and removal.
I think it should be preferable that you try using this interface and
report any missing feature first than allowing third party apps to hook
into the non-formalized and already complex auto-detector logic. I'll
close the ticket for the aforementioned reasons but feel free to gather
more feedback on your ML thread to demonstrate wide interest in this
feature.
--
Ticket URL: <https://code.djangoproject.com/ticket/30849#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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.64db85e6e634cc526585f6c5e0d7e7ac%40djangoproject.com.
