[DB-SIG] Database API clarifications
Thu, 29 Jan 1998 09:58:53 -0600
M.-A. Lemburg wrote:
> Tod Olson wrote:
> > >>>>> "B" == Bill Tutt <email@example.com> writes:
> > B> Generally the way to do this is just to have a seperate
> > B> getNextResult() API call that you call when your first result set
> > B> fetch*() calls return None.
> > So the next question to the SIG: should this mechanism (or some other)
> > for handling multiple result sets be included in the database API?
> Could you explain how you define multiple result sets with one
> SQL statement ? I'm not sure whether a cursor method is the right
> thing to add. Also, most DBs probably don't support this feature,
> so it should be optional from the APIs point of view.
Any database that supports compute clauses should return multiple result
sets. Sybase, for instance, does this.
Thomas Marsh firstname.lastname@example.org
Tivoli Systems, Inc. (512) 436 8643
DB-SIG - SIG on Tabular Databases in Python
send messages to: email@example.com
administrivia to: firstname.lastname@example.org