DBI cursor behaviour with multiple statements?
gerhard.haering at gmx.de
Fri Sep 27 12:01:44 EDT 2002
* Henrik Weber <Henrik.Weber at sys.aok.de> [2002-09-27 02:37 -0700]:
> I'm trying to write a DBI2 compliant module for Microsoft Access
Ok. Then the Database SIG's mailing lists is the appropriate place to
ask. You'll find that almost all module authors and many users are
> Now I'm not quite sure how to interpret the DBI2 specification when it
> comes to the execution of multiple data returning statements with the
> same cursor.
The behaviour is undefined for more than one DQL statement. And
.nextset() isn't meant for this case, either.
In fact, I asked the same question on the SIG's mailing list some time
Date: Tue, 28 May 2002 21:36:47 +0200
To: Python DB-SIG Mailing List <db-sig at python.org>
Subject: [DB-SIG] Multiple Statements
Message-ID: <20020528193647.GA902 at lilith.my-fqdn.de>
... and was referred to a discussion about a year ago (then), where the
consensus was what I summarized above.
Here's the SIG's mailing list: http://python.org/sigs/db-sig/
Btw. an updated form of the specification several interesting "optional
features" is available as PEP 0249.
More information about the Python-list