Hi!
> "Tim" == Tim Bunce <[EMAIL PROTECTED]> writes:
Tim> On Fri, Feb 02, 2001 at 05:48:41PM +0100, Marcello Giovagnoli wrote:
>> >
>> > Do you mean that mysql_store_result() should store everything to a
>> > local file and and mysql_fetch... should read from this file?
>> > This should not
Hi!
> "Marcello" == Marcello Giovagnoli <[EMAIL PROTECTED]> writes:
>> Do you mean that mysql_store_result() should store everything to a
>> local file and and mysql_fetch... should read from this file?
>> This should not be that hard to do.
Marcello> Yes, you can use the actual SQL_CURSOR
On Fri, Feb 02, 2001 at 05:48:41PM +0100, Marcello Giovagnoli wrote:
> >
> > Do you mean that mysql_store_result() should store everything to a
> > local file and and mysql_fetch... should read from this file?
> > This should not be that hard to do.
Like SQL_BUFFER_RESULT, but at the client inst
>
> Do you mean that mysql_store_result() should store everything to a
> local file and and mysql_fetch... should read from this file?
> This should not be that hard to do.
>
Yes, you can use the actual SQL_CURSOR_FORWARD_ONLY that is
unused at this moment, to call mysql_store_result_on_file()
Hi!
> "Marcello" == Marcello Giovagnoli <[EMAIL PROTECTED]> writes:
Marcello> Hi Monty,
>> Why do you need to retrieve so many rows to the client? Can't you use
>> LIMIT to restrict the number of result rows?
Marcello> The point is that the program scans the entire table and process each
Hi Monty,
> Why do you need to retrieve so many rows to the client? Can't you use
> LIMIT to restrict the number of result rows?
The point is that the program scans the entire table and process each row
in a diffrent way, executing other queryes inside the main SQLFetch() loop.
Someting like th
Marcello Giovagnoli writes:
> Hi Monty,
>
> > Why do you need to retrieve so many rows to the client? Can't you use
> > LIMIT to restrict the number of result rows?
>
> The point is that the program scans the entire table and process each row
> in a diffrent way, executing other queryes
