heh, I was saying it backwards [lack of sleep] but this is what I was referring to ...
"Note that if the database supports an auto-commit feature, this must be initially off. An interface method may be provided to turn it back on." - http://www.python.org/dev/peps/pep-0249/ ...yes psycopg complies, but sqlalchemy does not expose its interface method to turn autocommit functionality back on. Am I missing it somewhere? I don't see this exposed anywhere in the psycopg dialect nor create_engine(). Deadlocks are not fun to debug. On 2/1/07, Jonathan Ellis <[EMAIL PROTECTED]> wrote: > > On 2/1/07, Kumar McMillan <[EMAIL PROTECTED]> wrote: > > the fact that the deadlock was solved when I added the connection to > > the transaction tells me that psycopg runs in commit mode > > automatically (even though dbapi 2 says it should not). The psycopg > > docs reinforce this too : > > http://www.initd.org/tracker/psycopg/wiki/psycopg2_documentation#setting-transaction-isolation-levels > > > > Wrong; psycopg2 does not autocommit by default. It automatically > _creates new transactions_ but you still have to explicitly commit() > or rollback(). This is what DBAPI2 calls for (and is really the only > sane thing to do in non-autocommit mode if you think about it). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" 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/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
