#2688: failed save() with postgresql sometimes doesn't throw error until next
statement (which is 'set time zone')
--------------------------------------------------------+-------------------
Reporter: [EMAIL PROTECTED] | Owner:
nobody
Status: new | Component:
Database wrapper
Version: SVN | Resolution:
Keywords: psycopg transactions timezone postgresql | Stage:
Accepted
Has_patch: 0 | Needs_docs:
0
Needs_tests: 1 | Needs_better_patch:
0
--------------------------------------------------------+-------------------
Changes (by mir):
* summary: failed save() doesn't throw error until next statement (which
is 'set time zone') => failed save() with
postgresql sometimes doesn't throw error until
next statement (which is 'set time zone')
* needs_tests: 0 => 1
* stage: Unreviewed => Accepted
Comment:
As far as I know, the reason why sometimes an error is not detected with
postgresql before the {{{set timezone}}} is still unknown, but I have seen
enough reports in the mailing lists that I'm sure this is an issue. Any
help in sorting this out appreciated. If you can provide a reproducible
test case, please describe it here!
--
Ticket URL: <http://code.djangoproject.com/ticket/2688#comment:2>
Django Code <http://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 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
-~----------~----~----~----~------~----~------~--~---
