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,
firstly thanks for your answer, [EMAIL PROTECTED] works very very well !
We are doing a very hard work with mySQL , used as main database inside
our ERP Oasi. (instead of DB2 or ORACLE).
We have a performance problem with memory usage.
the process accesses to database via ODBC
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
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 row
Marcello
