Split multi-statement SQL for cloud service query

[sdairs]

What

cloud service query --queries-file sent a whole .sql script as a single sql body, so ClickHouse rejected it with error 62 (Multi-statements are not allowed) and only single-statement files worked.

The Cloud Query API has no native multi-statement mode to prefer instead: POST /service/{id}/run carries one sql string, and the server-side parser is what rejects the second statement. So the CLI splits the script.

• New crates/clickhousectl/src/cloud/sql_statements.rs — a lexical scanner that finds only the ; characters that really are separators. It skips over single-quoted literals, double-quoted and backtick-quoted identifiers (handling both \' and '' escapes), -- line comments, /* */ block comments, and $tag$ heredocs. A trailing ; produces no statement, whitespace/comment-only chunks are dropped, and everything else is sent verbatim (comments included). Unterminated quotes/comments/heredocs run to the end of input so the server reports the syntax error on the text the user actually wrote.
• service_query executes the statements sequentially and stops at the first failure, naming it: statement 2 of 5 failed: .... A single-statement run's errors are unchanged (no prefix).
• Credential resolution — including lazy Query API endpoint/key provisioning, the stale-stored-key refusal, and --no-auto-enable — now happens once on the first statement and the resolved credential is reused for the rest, so a script can never re-probe authorization or re-provision a key per statement. This is the reason for the QueryTarget/ResolvedQueryAuth refactor in services.rs; the auth precedence itself is untouched.
• Splitting applies to --query and stdin as well, so all three SQL sources behave alike. The visible consequence is that a script's trailing newline/; is trimmed before it is sent.
• A script whose SQL is only comments now fails with the SQL provided contains no statements to run before any network access.

Why

The flag is plural and a .sql file is the obvious thing to hand it; failing with a server-side parser error was the bug reported in #610. There is no transaction, so a failed script leaves earlier statements applied — --help and the README now say so explicitly.

Tests

• 22 splitter unit tests (cloud::sql_statements::tests): quotes and quoted identifiers, backslash and doubled-quote escapes, comments containing separators, heredocs and an unclosed $ marker, unterminated literals, a trailing backslash (no panic), multibyte content, trailing/duplicate separators, comment-only input, and a realistic schema script.
• Unit tests for the statement-number prefix, including that it preserves CloudErrorKind (so a 401 during a script still exits 4).
• Wiremock subprocess tests in cli_request_shape_test.rs: one request per statement in order with the exact bodies; failure on statement 2 of 3 exits 1, prints statement 2 of 3 failed, and never sends statement 3; a single-statement failure carries no prefix; a comment-only script hits no mock at all. Updated the existing SQL-sources test for the now-trimmed bodies.
• cargo fmt --all, cargo clippy --workspace --all-targets -- -D warnings, cargo test -p clickhousectl all clean. clickhouse-cloud-api was not touched.

Docs

cloud service query --help and README cover splitting, the quoting/comment rules, first-failure semantics, the absence of a transaction, and the per-statement OK acknowledgement for statements with no result body.

Stacked PR

Part of a stacked chain: this PR is based on fix/611-private-endpoint-id-validation, not main.

Fixes #610

🤖 Generated with Claude Code

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 70f7ad5. Configure here.}

[cursor]

FORMAT payloads split on inner semicolons

High Severity

The splitter treats every top-level ; as a statement boundary, including those in the raw payload after INSERT ... FORMAT (CSV, TSV, JSONEachRow, and similar). A single insert that previously went to the Query API as one body is now several requests, so the first fragment can apply truncated rows and later fragments run as SQL.

Additional Locations (1)

• crates/clickhousectl/src/cloud/services.rs#L2366-L2371

 

^{Reviewed by Cursor Bugbot for commit 70f7ad5. Configure here.}