On Wednesday 22 August 2007 00:37, Wolfram Hinderer wrote: > 2007/8/21, johnf <[EMAIL PROTECTED]>: > > As I read the code "crs.execute(sql, prm)" updates the db (and it in fact > > it does update the data). While doing so a transaction is started. I > > assume that is true from Ed's prior statements on SQLite not needing a > > "begin". But when the "self._cursor.commitTransaction()" fires - I get > > an error. The error is there is no transaction started (as I reported in > > the earlier email). > > > >From http://www.sqlite.org/lang_transaction.html : > > "Any command that changes the database (basically, any SQL command > other than SELECT) will automatically start a transaction if one is > not already in effect. Automatically started transactions are > committed at the conclusion of the command." > > There is no need for a begin, and there is no need for a commit. The > transaction is already committed when you try to commit. The error > message tries to say just that. > > If your want a multi-command transaction I guess you'll have to use > explicit transactions. > > Wolfram Wolfram Thanks for the information and for taking the time. It explains the results I was getting from dPref.py. I would have never guessed that SQLite had auto commits. -- John Fabiani
_______________________________________________ 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/dabo-dev/[EMAIL PROTECTED]
