Yesterday I was working with some code that needed a select ... for
update concept to avoid a race condition.
Adding .with_lockmode('update') works a treat on InnoDB and Postgres,
but for sqlite I end up having to sneak in a if session.bind.name ==
'sqlite'; session.execute('begin immediate
SQLite doesn't have support for SELECT..FOR UPDATE, and with_lockmode()
ultimately has no impact when using SQLite as nothing is rendered. SQLite's
concurrency model is based on a lock of the entire database file - hardly a row
lock - I wouldn't think such a strategy applies on that backend ?
Is this pysqlite issue about SELECT not starting a transaction related?
http://code.google.com/p/pysqlite/issues/detail?id=21
--
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to sqlalchemy@googlegroups.com.
To
