keith cascio wrote: > Michael > > On Mar 25, 1:50 pm, "Michael Bayer" <[email protected]> wrote: >> SQLA uses the DBAPI in its default mode of "autocommit=False" and is >> always going to issue flushes followed by a COMMIT or ROLLBACK. >> There's also a ROLLBACK which occurs automatically via the connection >> pool and you can turn that one off with a connection pool flag. But >> these operations are practically free with MyISAM so there's no overhead >> consideration. > > Thank you for the informative explanation. However, BEGIN/COMMIT/ > ROLLBACK are absolutely not free in my case. I'm dealing with > significant network latency because the database server is on another > continent and also the server itself is beleaguered. It is very > expensive to touch the database at all, even for what amounts to a "no- > op". I want to turn off the issuing of transaction statements. I am > able to do so with other database abstraction layer software.
SQLAlchemy also doesn't issue BEGIN. You might want to look at setting autocommit to false on your MySQLdb connection, since that's the layer that would be sending out BEGIN. > > Thank you for all your help, > Keith > > -- > 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. > > -- 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.
