#2688: failed save() doesn't throw error until next statement (which is 'set
time
zone')
-------------------------------------+--------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Type: defect | Status: new
Priority: normal | Milestone:
Component: Database wrapper | Version: SVN
Severity: normal | Keywords: psycopg transactions
timezone postgresql
-------------------------------------+--------------------------------------
I was getting a 'programmingerror' when the session middleware tried to
set the timezone, but as this works any other time it changes the session,
I assumed that wasn't the real problem. executing the set time zone
statement in psql worked too, so it seemed to be an earlier statement that
was causing the error. I eventually tracked down the earlier statement
that was causing the error (trying to set a DateField to a time.time()
rather than a datetime instance) but what I don't understand is why this
error wasn't reported when it happened.
I wondered if it was something to do with autocommit not happening until
after the session had been updated so I used the manual transaction
decorator to ensure the transaction was commited, but still no error. I
noticed in ticket 852, [EMAIL PROTECTED] talks about the same
behaviour. is psycopg not reporting the errors or is this a problem in
django?
--
Ticket URL: <http://code.djangoproject.com/ticket/2688>
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
-~----------~----~----~----~------~----~------~--~---
