executemany ('SELECT ...') (was: [DB-SIG] DBAPI-2.0 clarifica tions)

Federico Di Gregorio fog@mixadlive.com
Tue, 20 Mar 2001 12:04:28 +0100

Scavenging the mail folder uncovered Dittmar, Daniel's letter:
> I think this is true only when the choosen standard is based on experience.
> Until then, I prefer
> - to document the behaviour as implementation defined
> - provide example code to achieve either behaviour which helps to gain
> experience
> - if after some time a consensus arises about the 'right' behaviour, then it
> can be put into the standard

i agree.

> In this case (executemany of a SELECT), I see three possible alternatives
> a) multiple result sets, where each result sets matches to exactly one set
> of input parameters
> b) exactly one result set, which is the union of the SELECTs
> c) an undefined number of result sets with identical structure, where there
> is no defined relation between each result set and a specific set of input
> parameters

both a and b seems good to me. can you explain what an "array select" is
and why choosing (a) would "hide" it on sap and oracle?  


Federico Di Gregorio
MIXAD LIVE Chief of Research & Technology              fog@mixadlive.com
Debian GNU/Linux Developer & Italian Press Contact        fog@debian.org
              La felicitÓ Ŕ una tazza di cioccolata calda. Sempre. -- Io