FreeTDS Development Group

["SourceForge.net" <noreply AT sourceforge.net>]

Patches item #1083180, was opened at 2004-12-10 14:59
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=407808&aid=1083180&group_id=33106

Category: db-lib
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Adrian Daley (agd)
Assigned to: Nobody/Anonymous (nobody)
Summary: dbresults could return NO_MORE_RESULTS multiple times

Initial Comment:
Hi,

A wrapper layer around the db-lib calls in our
application has a side effect of calling dbresults
after NO_MORE_RESULTS has already been returned.

Here's an example.  In our wrapper layer
the two dbresults calls are in different functions.

while (dbresults(dbproc) != NO_MORE_RESULTS) {
        /* process results */
}
if (dbresults(dbproc) != NO_MORE_RESULTS) {
        /* shouldn't ever get here */
}

The Sybase implentation of dbresults will continue
to return NO_MORE_RESULTS when dbresults is called
multiple times.  The attached patch implements the
same behavior and updates the t0002 test case to
verify it.  The change counts on the fact that
the functions that execute a new server command
reset dbproc->dbresults_state to _DB_RES_INIT.

Thank you for considering this patch.

Adrian Daley
Silicon Graphics

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=407808&aid=1083180&group_id=33106