Multi statement support about trilogy HOT 1 CLOSED

Not that it was requested (😇), but here's my own input on this:

IMHO I think this should be something that is exposed on the higher level bindings only. The C API is (or at least was) designed to be intentionally lower-level - a lot closer to the protocol - so that other bindings could be built on top in a more flexible way. The C API also intentionally doesn't perform any buffering (outside of a single packet). So anything beyond that is also up to the higher level bindings to handle (like buffering the resultset before returning to the caller). So doing something akin to libmysqlclient's store_result down in the C API feels wrong (to me). With my current understanding of the protocol, our C API already exposes everything we'd need to build this into higher level bindings (Ruby being the only one included in this repo).

Adding something like Trilogy#next_result seems like it could be made pretty clean 👍. Some of the internals of execute_read_query could probably be split out into that and then reused there as well?

from trilogy.