Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #81670 > unrolled thread

Re: Db transactions and locking

Started byChris Angelico <rosuav@gmail.com>
First post2014-11-28 17:58 +1100
Last post2014-11-28 17:58 +1100
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Db transactions and locking Chris Angelico <rosuav@gmail.com> - 2014-11-28 17:58 +1100

#81670 — Re: Db transactions and locking

FromChris Angelico <rosuav@gmail.com>
Date2014-11-28 17:58 +1100
SubjectRe: Db transactions and locking
Message-ID<mailman.16397.1417157933.18130.python-list@python.org>
On Fri, Nov 28, 2014 at 5:57 PM, Frank Millman <frank@chagford.com> wrote:
> cur.execute('commit') tells the database to commit the transaction, but the
> adaptor is not aware of this, so does not reset. Therefore the next command
> does not trigger starting a new transaction.
>
> I have now learned another lesson - never use cur.execute('commit'), always
> use conn.commit()

Without looking in the source I can't be sure, but that seems very logical.

ChrisA

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web