Ed Leafe wrote: > On Apr 17, 2008, at 11:27 AM, Carl Karsten wrote: > >> I am pretty sure the lock will block even SELECT queries. which >> would be really >> bad. > > > First off, transactions are not locks. Transactions are used all the > time without applications grinding to a halt.
Transactions that only cover the time it takes some code to run, yes. for transactions that span waiting for a user, there must be some reason it is discouraged, and 'grind to a halt' is pretty much the only reason I can think of. > > Second, many DBs use implicit transactions; if you look at the code > for dbPostgreSQL.py, beginTransaction() does nothing but log the call. Then what actually defines the span of the transaction? I thought it was whatever .execute() did, which could be multiple commands or a SP. 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]
