[DB-SIG] Database API clarifications
Thu, 29 Jan 98 09:20:08 -0600
Multiple result sets are commonly returned from stored procedures, but you
can also send multiple select statements at one time. My noncompliant
sybase module always returns a list of result sets (although there is
usually only only item in the list).
(not speaking for any current or future Swiss Bank)
> Tod Olson wrote:
> > >>>>> "B" == Bill Tutt <firstname.lastname@example.org> 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.
> Marc-Andre Lemburg
> DB-SIG - SIG on Tabular Databases in Python
> send messages to: email@example.com
> administrivia to: firstname.lastname@example.org
DB-SIG - SIG on Tabular Databases in Python
send messages to: email@example.com
administrivia to: firstname.lastname@example.org