#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: |
------------------------------+---------------------------------------------
Changes (by Thomas Steinacher <[EMAIL PROTECTED]>):
* status: closed => reopened
* resolution: invalid =>
* component: Generic views => Database wrapper
* summary: problem with login - transaction is aborted => PostgreSQL
backend reporting "SET TIME ZONE" error instead
of the real error
Comment:
''"The traceback above is the result of a previous error. It's impossible
to say what has caused it without more information."''
Yeah, and THIS is the bug. It is PostgreSQL related. Django should report
the real error (the previous error), like on other database backends, and
not the "SET TIME ZONE" error. There is no way to say what the previous
error was without using some crappy print-statements. It is impossible to
develop using the PostgreSQL backend.
--
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
-~----------~----~----~----~------~----~------~--~---
