Multi-Results Support

[julienschmidt]

Currently the driver returns the first result if there is more than one.
Would it make more sense to return the last result instead?

CREATE TABLE example (num INT); INSERT INTO example VALUES (1), (23), (42); UPDATE example SET num = num+10 WHERE num < 25

I assume that usually the last statement is the one you care about. Any thoughts?

[PuppyKhan]

Not necessarily. With stored procedures, the last result is not the last query, but an additional acknowledgement afterwards.

[arnehormann]

It's simpler to move the query you are interested in to the last position. I have some SET @VAR := ... queries that prepare a session context for a SELECT and I'd primarily use the multi result feature for these. It's pretty hard to rewrite these queries with SELECT as the first statement.

I'm all for the last one. But formed slightly different: always return the last result matching the call type; counts for Exec, rows for Query.

I have add I'm not sure yet if it's possible to differentiate between Exec and Query with an emptyRows result.

[julienschmidt]

Looks like we can have proper Multi-Results Support in Go 1.8: golang/go@86b2f29

[bkubiak]

+1 for this long-awaited feature, we are using sets of prepared stored procedures that return multiple results.

[julienschmidt]

v1.3 has just been tagged and the master branch is open to potentially less stable changes again. I'd be very glad to accept a pull request on this!

If someone (including a new face) wants to work on this, please let us know!