#27162: Move CreateExtension to django.db.backends.postgresql
-------------------------------------+-------------------------------------
Reporter: claudep | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by timgraham):
I understand the purity behind the rationale, but the new import path
(`django.db.backends.postgresql.migrations.operations.CreateExtension`)
seems a bit unwieldy. I guess the pattern looks better for third-party
backends that don't have "django.db.backends" in the import path. Also, I
think this is the first time we would have users importing code directly
from a database backend. I guess that's a more common pattern for third-
party backends which may provide custom fields. It raises the question why
we have `contrib.postres` instead of putting that in the backend though.
Is it impossible to import from the current location without adding
`contrib.postgres` to `INSTALLED_APPS`?
--
Ticket URL: <https://code.djangoproject.com/ticket/27162#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/065.b8a89c3556ce3b8fb4dc6b77cca935e7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
