On Apr 27, 10:41 am, Michael Bayer <[email protected]> wrote:
>
> then yes, for your case this is exactly the pysqlite bug Daniel mentions:
> http://code.google.com/p/pysqlite/issues/detail?id=21. Pysqlite doesn't open
> the transaction until DML is encountered specifically to reduce file locks.
> This should be configurable, as well as the type of BEGIN emitted.
> SQLAlchemy itself never emits BEGIN.
oic, so if pysqlite was doing the right thing with the explicit BEGIN
I would expect to be able to do something like this:
engine = create_engine('sqlite:///foo.db',
connect_args={'isolation_level': 'IMMEDIATE'})
... and all connections would automatically issue the correct begin
statement and acquire a reserved lock at the beginning of the
transaction. But as it is, they don't do anything until they get down
to the update, and it's kind of a disaster.
Thanks for the info,
-clayg
--
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.
