>
> 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().
This new funcion open a temporary file and perform
the same operation of mysql_store_result() but it uses
the temporary file instead of the memory.
It sets a flag to tell to the native mysql function (I don't
remember its name now) called in SQLFetchRow()
to read from the temporary file instead of memory.
This is easy to do, (for you of course) but it could
be a trick waiting the cursors that, If I don't mind,
are planned in mySQL 4.
One can activate or deactivate this capability using
ODBC or SET SQL_PARAMETER=0|1
Do you think that you can insert this feature in a
3.23.33 releases without modify yours planned jobs
and, if yes, please let me know when you can do it.
Regards
marcello
P.S.
Do you remember my friend Danilo Montesi (University of Milan),
he has sent to you an abstract to the Triggers implementation
one or two month ago ?
I would like to know your opinion on his job, and if you
consider this approach convenient.
--
Marcello Giovagnoli
R & D
Logical System S.r.l.
23, Via R. Scotellaro
I-60035 Jesi (AN) -ITALY
Tel/Fax: +39 731 200374/200378
mailto:[EMAIL PROTECTED]
http://www.logicalsystem.it
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
