#3179: PostgreSQL backend reporting "SET TIME ZONE" error instead of the real
error
------------------------------+---------------------------------------------
Reporter: anonymous | Owner: adrian
Type: defect | Status: reopened
Priority: normal | Milestone:
Component: Database wrapper | Version: SVN
Severity: normal | Resolution:
Keywords: |
------------------------------+---------------------------------------------
Comment (by ubernostrum):
What's a bit weird about this is that there's nowhere in our PostgreSQL
backend that I can spot which would trap errors; I can't say definitively
one way or another, but it might be worth looking upstream at psycopg as
well, since it should -- as far as I know -- be raising
`OperationalError`, `ProgrammingError` or `IntegrityError` and we don't
catch those.
--
Ticket URL: <http://code.djangoproject.com/ticket/3179#comment:>
Django <http://code.djangoproject.org/>
The web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
