Opened 10 years ago
Closed 10 years ago
#22883 closed Cleanup/optimization (duplicate)
Unhelpful GeoDjango error message when credentials are invalid
| Reported by: | anonymous | Owned by: | nobody |
|---|---|---|---|
| Component: | GIS | Version: | 1.6 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | yes |
| Easy pickings: | no | UI/UX: | no |
Description
I went through the GeoDjango tutorial several times this evening not realizing that my Postgres credentials were incorrect. The error message it gave me lead me to believe it was a versioning problem and not a DB connection issue:
django.core.exceptions.ImproperlyConfigured: Cannot determine PostGIS version for database "blanket". GeoDjango requires at least PostGIS version 1.3. Was the database created from a spatial database template?
I believe the right thing to do would be to include the raw DB error.
Change History (5)
comment:1 by , 10 years ago
| Summary: | Unhelpful GeoDjango error message → Unhelpful GeoDjango error message when credentials are invalid |
|---|
comment:2 by , 10 years ago
comment:3 by , 10 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:4 by , 10 years ago
| Easy pickings: | unset |
|---|---|
| Has patch: | set |
| Patch needs improvement: | set |
| Type: | Bug → Cleanup/optimization |
Related pull request that previously didn't have a ticket.
comment:5 by , 10 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
This is in fact a duplicate of #21504, where the catched exception was changed from DatabaseError to ProgrammingError to let those credential-specific issues slip through. This will be available in Django 1.7. Thanks for the patch and report anyway.
This thing won't let me include my email address but it's floydophone@….