subsequent transaction errors should display properly

[refset]

Currently a subsequent error may look like a "Statement succeeded" or a repetition of the earlier results entry

Confusing example found in the wild

What's actually happening:

[refset]

Finally getting somewhere...

PostgreSQL's Behavior with Failed Transactions

If a statement within a transaction (BEGIN ... COMMIT) fails in a way that PostgreSQL marks the transaction as failed, subsequent statements in the same transaction will not execute. Instead, they will return a default response until the transaction is explicitly rolled back.

This means if a transaction is in a failed state, JDBC might not actually be executing further statements, and instead, it might be returning an unintended previous result.

Admittedly this could all be ChatGPT hallucinations:

JDBC Connection Corruption

A no prepared statement error suggests that JDBC is in a broken state, likely due to how transactions are handled.
If the connection is implicitly closed or reset, then xtdb/jdbc-execute! might be executing on an invalid connection.
Result? Later tx batches might be inadvertently reusing old results because their execution is failing silently.

[refset]

I'm fairly sure this is actually a more fundamental pgwire/JDBC issue, and not Play misbehaving - i.e. the scope of xtdb/xtdb#4169 needs to be widened