FreeTDS Development Group

[James K. Lowden <jklowden AT speakeasy.org>]

> > On Sat, 6 Apr 2002 20:39:47 -0500 "Fernando" <nulll AT bol.com.br> wrote:
> > > 
> > >    If I submit a statment(select) that return 100.000 lines, I can
> > >    fetch group of lines or I have wait by all lines ?
> > 
> > The server listens to your query and composes a result set.  If the
> > result set is not sorted (no ORDER BY), the server will start
> > returning rows as soon as it finds some that meet your criteria.  If
> > the result set *is* sorted, the server has to wait until it finds all
> > your rows, then sort them, then send you the rows.  Frequently,
> > sorting leads to waiting.  
> > 
> > Does that answer your question?

On Sat, 6 Apr 2002 23:39:20 -0500 "Fernando" <nulll AT bol.com.br> wrote:
>
>    More or less. The result set can are in server and I fetch a group of
> lines by time until end ? Can I send to my client application lines of
> result set by solicitation hers ?
>    I want that part of result set stay on server until my client
> application need more a group of lines.
> 
> Is this possible ? 

Fernando, 

You're talking about the TDS protocol itself, yes?  Not dblib, ctlib, or
ODBC?  AFAIK, TDS never buffers a row.  A result set row is on the server
until you fetch it.  When you fetch it, it leaves the server and comes to
the client.  

My answer assumes you want to fetch the rows in order, 1..N.  If you want
to skip rows or read them out of order, things get more interesting.  

HTH.

--jkl