#33885: Drop automatic PostGIS extension creation on PostGIS backend
-------------------------------------+-------------------------------------
Reporter: Johannes | Owner: nobody
Maron |
Type: | Status: new
Cleanup/optimization |
Component: GIS | Version: 4.0
Severity: Normal | Keywords:
Triage Stage: | [email protected]
Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 1
UI/UX: 0 |
-------------------------------------+-------------------------------------
Thanks to our friends at Heroku, we currently can't execute `create
extension` without our database throwing an error.
That made us aware of the fact, that the database wrapper for PostGIS
execute a SQL statement every time it prepares the database.
That behavior seems inconsistent with how any other PG extension works.
Usually, those have to be initialized in a migration explicitly. There has
been a debate in the past, if that statement can do any harm, but clearly
Heroku has proven it can. Therefore, I would suggest deprecating this
behavior and schedule it for deletion in Django 5.
Superseeds #28975
--
Ticket URL: <https://code.djangoproject.com/ticket/33885>
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/010701825dd0011b-92c0e9d0-5715-44ec-bc63-c6f7fb750869-000000%40eu-central-1.amazonses.com.
