[DB-SIG] Opened question ...
Sun, 8 Oct 2000 04:01:07 -0700
Most databases define commits on a connection basis. All changes from all
cursors will be committed. For example, you might have three cursors open,
each performing a single function. After their operation, you commit then in
bulk. The "parent" of all these cursors is the connection, which is where
the commit() method is defined.
On Sat, Oct 07, 2000 at 11:29:11PM +0200, Thierry MICHEL wrote:
> I put the follow motion for the DB-API, and I wait for your opinion about it :
> I would make a cursor object like a session to a database, to
> define the commit and the rollback functions into the cursor
> object instead of the connection object.
> A matter of fact, all works in the database are executed in a cursor
> so I don't understand why the commit and the rollback are outside it.
> I wait for comments about this motion.
> Thank you for your interest.
> Thierry MICHEL
> Mixadlive Developer
> ooOO*- PoPy Team Project Manager -*OOoo
> "Sainthood in the Church of Emacs requires living a life of purity,
> but in the Church of Emacs, this does not require celibacy."
> Richard Stallman.
> DB-SIG maillist - DB-SIG@python.org
Greg Stein, http://www.lyra.org/