What I forgot to mention in all that, is that SQLA also supports
SAVEPOINT very strongly. Using a SAVEPOINT-capable database opens up
your choices for being able to flush(), hit an error, and then retry
what you were doing, without a rollback of the overarching transaction
needed. We cal
On May 13, 2008, at 5:15 PM, Randall Nortman wrote:
> handling. I'm curious how SA handles this, especially transient
> errors where a retry is the right thing to do. For example, in
> several of my current sqlite apps (using bare DB-API), I get
> occasional locking errors ("Database is locked
