I mean, if you run a statement like "select 1; select 1" it fails. It does not support multiple SQL statements per individual JDBC call. Most other drivers do.
I would consider an implementation. But my question was more like "this is how it is, is there a reason, historical or not?" If there's no reason, and it's a thing the Calcite project would want, I would consider implementing it. ________________________________ From: Mihai Budiu <[email protected]> Sent: Tuesday, February 17, 2026 10:41 To: [email protected] <[email protected]> Subject: Re: JDBC Driver, parseStmtList? I have not used Calcite through the JDBC driver in this way. Can you provide a reproduction of the issue you are seeing? If this is a missing feature, you should consider filing a JIRA issue, and perhaps contributing an implementation? https://issues.apache.org/jira/projects/CALCITE Mihai ________________________________ From: Jerome Haltom <[email protected]> Sent: Monday, February 16, 2026 7:30 AM To: [email protected] <[email protected]> Subject: JDBC Driver, parseStmtList? I am working on an application that makes use of Calcite through the JDBC driver, and am hitting a problem with it being unable to parse multiple semi-colon separated statements. My investigations tell me this isn't supported. parseStmt is invoked on the parser, not parseStmtList. And of course the rest of it isn't built to deal with multiple statements, tracking multiple resultsets, etc. I guess my first question would be, why? Is there a reason for this as it stands, or is it just that nobody has gone through an added support for multiple statements since that was added?
