#28975: Skip automatic creation of postgis extension if it already exists
-------------------------------------+-------------------------------------
Reporter: sphrak | Owner: sphrak
Type: | Status: new
Cleanup/optimization |
Component: GIS | Version: 2.0
Severity: Normal | Resolution:
Keywords: create extension, | Triage Stage: Accepted
postgis, psycopg2, postgresql |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak):
Other extensions are needed to unlock various features on some PostgreSQL
versions. `postgis` is always required for
`django.contrib.gis.db.backends.postgis`, so IMO it's not the same case.
We would force all users to manually create a migration with
`PostGISExtension()` when starting to work with GIS on PostgreSQL. What do
you think about my [https://code.djangoproject.com/ticket/28975#comment:9
proposition]?
--
Ticket URL: <https://code.djangoproject.com/ticket/28975#comment:11>
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/010701825dfa324d-31aaf0d3-dca5-4034-b324-e3886018a717-000000%40eu-central-1.amazonses.com.
