In experimenting with libdrizzle, I ended up being surprised by the fact
that drizzle_query, in the default blocking mode, waits for some sort of
result data to come back from the server. Why does this occur? Is it
needed? It seems to me that drizzle_query should just send the query,
and the result reading functions such as drizzle_result_buffer should
actually wait for data back from the server.
This would allow me to dispatch a bunch of small queries in parallel,
then use blocking reads to get the results. This would be somewhat
simpler than needing to put it in async mode and do that myself.
Also, I was surprised that drizzle_query_run and drizzle_query_run_all
call drizzle_result_buffer. I was expecting to have to do that. This
means I can't use the incremental reading functions with these "helper"
routines? I guess this is mostly a documentation issue.
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
