Ed Leafe wrote: > On Apr 17, 2008, at 10:38 AM, Paul McNett wrote: > >> Since nobody is using my app (yet) in a multiuser context (database >> is a >> sqlite db stored locally) I don't have a problem holding the >> transaction >> open forever. > > > It's really no different than a DB that begins a transaction > implicitly - they can be open for just as long. > > The difference here is that this is under developer control. Current > transaction behavior works as always; all that's changed is that you > can begin/commit/rollback from the UI, as you wanted to do.
note: my use of "sure" means I have nothing to back this up with, so I could be completely wrong. I am very sure this is not the intended use of transactions, and so the db engines are not going to take this kind of use into account, and thus there can be significantly undesirable side effects. I am pretty sure the implicit transactions are 'scoped?" for a single .execute(), where if you start a transaction, touch the db (delete some records) there will be some sort of lock on 'stuff' (no clue exactly what) until the user clicks something and the transaction is committed or rolled back. I am pretty sure the lock will block even SELECT queries. which would be really bad. Carl K _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[EMAIL PROTECTED]
