I looked at the patch, mostly looks good, I may touch a few things up. Thanks for the input!
As I mentioned in the other email, this interface code was experiemental and I plan on working the internals to be more flexible and give beter control. -Eric On Thu, Jan 21, 2010 at 12:34:43PM -0500, Evan Jones wrote: > When running single queries using drizzle_query_add and > drizzle_query_run, occasionally drizzle_run_query returns > DRIZZLE_RETURN_NO_ACTIVE_CONNECTIONS. The cause is that if things > are timed correctly, the initial call to drizzle_query (query.c:219) > returns DRIZZLE_RETURN_OK, instead of DRIZZLE_RETURN_IO_WAIT. In > this case, the code needs to call drizzle_result_buffer. This gets > complicated, because it duplicates the code in the switch below. > > I've added a patch to my branch. It is probably incorrect in some > way, but works for me. It moves the query state machine switch into > its own function. The initialization and the loop then both use this > state machine function. > > See: > > http://bazaar.launchpad.net/~evanj/libdrizzle/dev/revision/139 > > > Evan > > -- > Evan Jones > http://evanjones.ca/ _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
