On Tue, Aug 20, 2002 at 09:26:17AM +0100, [EMAIL PROTECTED] wrote: > PHP gets around this with odbc_close() which I believe $stmt->finish() could be > used for. The main problem would then be requiring scripts to call finish which > I guess would be undesirable. > > I'm not sure but I'd guess the number of poeple returning multiple result-sets > from procedures is few (partly based on the fact it was not working properly). > > It may be seen as a bit of a hack, but how about an attribute to say "we are > potentially fetching multiple result-sets" and in this case the statement is > marked inactive when [a] SQLMoreResults says there are no more result-sets or > [b] finish() is called (but this implies calling SQLFreeStmt(SQL_CLOSE)). If > this new attribute is not set (the default) it works as before. Anyone not > setting this new attribute but returning multiple result-sets and not consuming > them (no automatic call to SQLMoreResults now) will get an error with MS SQL > Server something like "busy with result-set on an another statement).
Seems reasonable. Would it also be worth having an attribute to say the application is interested (or not) in non-select row counts? That way the application need not both with having to skip them because the driver will. Tim [who's not been following in detail]
