DBI cursor behaviour with multiple statements?
Henrik.Weber at sys.aok.de
Mon Sep 30 10:19:11 CEST 2002
Gerhard Häring <gerhard.haering at gmx.de> wrote in message news:<mailman.1033143038.7112.python-list at python.org>...
> 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
> subscribed there.
Well, their archive is going to make interesting reading.
> > 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.
So I can take the easiest way out. I can live with that.
> 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.
> -- Gerhard
That sounds interesting. Thank you.
More information about the Python-list