Is there a way to exec a query without handling it as a prepared statement? about trino-go-client HOT 3 CLOSED

Why do you need to execute two queries in the same exec? This is generally not supported and is not related to preparing queries.

from trino-go-client.

I think it's done this way to avoid extra logic to check if there are any parameters for the query. Can you describe a use case when this is not desirable? Also, PRs are always welcome.

from trino-go-client.

Hi @nineinchnick, thank you for answering.
So, currently for our scenario, we need to change the insert_existing_partitions_behavior value to OVERWRITE for some given executions. So for this we have two choices:

1. in the same exec, we trigger 3 queries (one for changing the session var, one as the necessary exec, and one for changing the session var back )
2. create two trino client connections and determine which will trigger which queries. (we have a releation of ~80% needing APPEND and ~20% needing OVERWRITE.

But when we came to execute two queries in the same exec fot testing purposes, we got back the following error:

trino: query failed (400 Bad Request): "Invalid X-Trino-Prepared-Statement header: line 1:67: mismatched input ';'. Expecting: '%', '*', '+', '-', '.', '/', 'AND', 'AT', 'OR', '[', '||', <EOF>, <predicate>"

that's how we found out that every exec was sent as a prepared statement (and also read the trino.go file to confirm), therefore my treasure hunting.

I'll be looking for a way to enhance this behavior and possibly come back with good news :)

from trino-go-client.