On Jun 24, 2010, at 9:38 AM, Torsten Landschoff wrote:
>
> However, when passing this same option to create_engine, it has no
> effect. Which does not surprise me given that the documentation at
> http://www.sqlalchemy.org/docs/reference/dialects/sqlite.html only talks
> about sending a pragma down to each sqlite connection, while the
> misbehaviour seems to be caused by the sqlite3 module adding "commit"
> instructions into the command stream.
>
> More precisely, this code here automatically inserts a commit in front
> of all commands send to sqlite which are not select, update, delete,
> insert, replace:
>
> http://code.python.org/hg/branches/release2.6-maint/file/7fa70e059572/Modules/_sqlite/cursor.c#l571
>
>
> So, as a stop gap measure, how do I pass isolation_level=None to
> sqlite3.connect via SA?
just use connect_args, should be in the docs:
from sqlalchemy import *
e = create_engine('sqlite://', connect_args={'isolation_level':None})
c = e.raw_connection()
assert c.isolation_level is None
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to sqlalch...@googlegroups.com.
To unsubscribe from this group, send email to
sqlalchemy+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en.
