#24862: Patch for GeoDjango to improve error message if database connection is
bad
-------------------------------------+-------------------------------------
Reporter: brycenesbitt | Owner: sephii
Type: | Status: assigned
Cleanup/optimization |
Component: GIS | Version: master
Severity: Normal | Resolution:
Keywords: PostGIS, GeoDjango, | Triage Stage: Accepted
GIS, Usability |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by sephii):
Pull request is available here:
https://github.com/django/django/pull/4796/
Note that:
* I didn't include tests for this trivial change
* I wasn't able to reproduce the issue since it looks like that on newer
PostGIS versions PostGIS functions are always available
--
Ticket URL: <https://code.djangoproject.com/ticket/24862#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 [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/070.6b62888f074f48a6bb952358f790a18f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
