Skip to Content.
Sympa Menu

freetds - RE: [freetds] new dblibrary issue

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: "'FreeTDS Development Group'" <freetds AT lists.ibiblio.org>
  • Subject: RE: [freetds] new dblibrary issue
  • Date: Fri, 14 Feb 2003 12:29:20 -0500

> From: Thompson, Bill D (London) [mailto:ThompBil AT exchange.uk.ml.com]
> Sent: February 14, 2003 11:37 AM
>
> In other words, if you have fetched all the rows with
> dbnextrow, it is not
> necessary to "complete" the results processing before
> submitting another request.
>
> We don't like this, and return a "...results pending.." error message
>
> I've altered our code so that we behave the same as Sybase
> However this has invalidated dblibrary unittests t0004 and
> t0005, which hope to trap just this circumstance.

So, what will you do? Something like:

If dbsqlsend sees tds->status is PENDING
Peek at next token
If it's a "done" token
Read the packet
update tds->status
else return PENDING error
continue...

Or is that not it?

BTW, I just noticed that dbcancel() is a cheat. It doesn't send a cancel
message; it just reads all the rows. If you're interested in performance
and emulation of Sybase's libraries, that's not likely to be statisfactory
where large pending results sets are involved.

Regards,

--jkl


The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above. If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the
original message. Please note that we do not accept account orders and/or
instructions by e-mail, and therefore will not be responsible for carrying
out such orders and/or instructions.





Archive powered by MHonArc 2.6.24.

Top of Page