id,summary,reporter,owner,description,type,status,component,version,severity,resolution,keywords,cc,stage,has_patch,needs_docs,needs_tests,needs_better_patch,easy,ui_ux 2688,failed save() with postgresql sometimes doesn't throw error until next statement (which is 'set time zone'),mail@…,zefciu,"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, kkennedy@kenzoid.com talks about the same behaviour. is psycopg not reporting the errors or is this a problem in django?",Bug,closed,"Database layer (models, ORM)",dev,Normal,worksforme,psycopg transactions timezone postgresql,mail@… sam@…,Accepted,0,0,0,0,0,0