Please reply to [EMAIL PROTECTED] (not to me personally),
so that others can follow this thread.
At 18:55 -0700 10/6/03, Don Cohen wrote:
Paul DuBois writes:
> >Perhaps I misunderstood the doc but I thought by using _use_result
> >I was asking for the server not to send the next tuple until I as
At 18:09 -0700 10/6/03, Don Cohen wrote:
Paul DuBois writes:
> At 17:26 -0700 10/6/03, Don Cohen wrote:
> >http://www.mysql.com/documentation/mysql/bychapter/manual_Clients.html
> >says
> >
> > you must retrieve all the rows even if you determine in
> > mid-retrieval that you've found the
Paul DuBois writes:
> At 17:26 -0700 10/6/03, Don Cohen wrote:
> >http://www.mysql.com/documentation/mysql/bychapter/manual_Clients.html
> >says
> >
> > you must retrieve all the rows even if you determine in
> > mid-retrieval that you've found the information you were looking
> > for.
At 17:26 -0700 10/6/03, Don Cohen wrote:
http://www.mysql.com/documentation/mysql/bychapter/manual_Clients.html
says
you must retrieve all the rows even if you determine in
mid-retrieval that you've found the information you were looking
for.
My question is: why?
Because there is no provision
http://www.mysql.com/documentation/mysql/bychapter/manual_Clients.html
says
you must retrieve all the rows even if you determine in
mid-retrieval that you've found the information you were looking
for.
My question is: why?
In fact I thought that the normal interface for a database would sho
