Use ExtractStatement to split query into multiple statements

[marcboeker]

Use ExtractStatement to split query into multiple statements

[begelundmuller]

I agree that b is too weird. Another alternative (let's call it d) would be to input the bound arguments only to the last statement. I wonder what the other DuckDB binding libraries (e.g. Python or Node) do?

Intuitively, I think a would make the most sense – I took a look, and I think we can use duckdb_nparams to distribute the args correctly over the statements as they're prepared and executed.

If there are multiple SELECT statements in one query string (which I would never do), I would expect to get the result of only the last SELECT statement (but the error of the first that failed, if any).

Generally though, I don't have much of a use case for doing multiple statements with bound args. The main use cases I can think of for multi-statement queries are when loading queries from a file (e.g. migrations) or receiving them from the user – in both cases, bound args are unlikely to be used. So c should also be fine.

[marcboeker]

Thanks for your detailed opinion. I agree with you, that having multiple SELECTs in one statement is kinda weird.

It seems, that the Python driver applies the given parameters to each query instead of distributing them.
The C++ API seems to have the identical behavior. This is similar to b.

And the Python driver also returns the result of the last statement.

I think I need to do more research on this to prevent total confusion.

[begelundmuller]

If that's what the official drivers do, I would probably just do the same for Go :)