Why is mysql_next_result() a required call? (was Re: Example of Cluster SLOWER than InnoDB -- help?)
I'm now getting about 140m/s on my (crappy) hardware.
I save all queue operations until commit and do them all as one multiple statement query.
I'm spending about 1.7ms on each call to mysql_next_result(), which seems to indicate communication to the server for each call. Doesn't this negate the benefit of multiple statements?
If I don't call mysql_next_result() then a future query results in "Lost connection to MySQL server during query".
Is there an asynchronous API to MySQL?
Subject
Views
Written By
Posted
6565
December 07, 2004 11:48AM
3189
December 07, 2004 02:41PM
3306
December 07, 2004 07:42PM
3037
December 08, 2004 11:14AM
3082
December 08, 2004 04:50PM
Why is mysql_next_result() a required call? (was Re: Example of Cluster SLOWER than InnoDB -- help?)
5646
December 09, 2004 02:45PM
3041
December 07, 2004 03:39PM
3028
December 07, 2004 08:13PM
3023
December 07, 2004 11:51PM
3024
December 08, 2004 12:36AM
3147
December 08, 2004 03:55PM
3180
December 08, 2004 06:14PM
2988
December 08, 2004 09:27PM
3045
December 08, 2004 05:05PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.