#31693: Add setting to control installed PostgreSQL extensions.
-------------------------------------+-------------------------------------
Reporter: Markus Bertheau | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Migrations | Version: master
Severity: Normal | Resolution: wontfix
Keywords: | 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: new => closed
* resolution: => wontfix
* component: Database layer (models, ORM) => Migrations
Comment:
> Maybe extensions should be configured in settings.DATABASES and then
automatically installed by the postgresql engine.
`CreateExtension()` is a normal database migration operation, we shouldn't
treat it differentially. If you don't want to (or cannot) control creating
extensions with migrations then you can create them directly in a
database.
--
Ticket URL: <https://code.djangoproject.com/ticket/31693#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.9f84f49b99e2949d4e208ec0dfe0b2eb%40djangoproject.com.
