Skip to content

test(query): add regression coverage for escaped/doubled quote handling in SQL parser - #70

Merged
ZhuchkaTriplesix merged 1 commit into
devfrom
issue/59-escaped-doubled-quote-handling
Sep 29, 2026
Merged

ZhuchkaTriplesix merged 1 commit into
devfrom
issue/59-escaped-doubled-quote-handling

Conversation

@ZhuchkaTriplesix

Copy link
Copy Markdown
Member

Summary

  • strip_sql_comments_and_trim and split_sql_statements in src/rpc/handlers/query.rs already handle backslash-escaped quotes (\') and SQL-standard doubled quotes ('') inside string literals correctly — this was fixed as a side effect of the Safe Mode multi-statement bypass fix (fix(security): prevent Safe Mode precheck bypass on multi-statement SQL queries #54, commit 751393e), which rewrote the in_string branch of both functions to consume the escape/doubled-quote pair instead of treating the first quote as a closing quote.
  • No production code change is needed; this PR adds regression tests covering the exact failure scenarios described in fix(parser): handle escaped and doubled quotes in SQL comment stripper and Safe Mode lexer #59 (escaped quote followed by -- , and a doubled-quote literal), for both the low-level parser functions and the enforce_safe_mode_precheck integration path, to lock in the current correct behavior and document that it's intentional.

Closes #59

Test plan

  • cargo test — 93/93 passing, including the 3 new tests added here
  • cargo fmt --all -- --check
  • cargo clippy --all-targets --all-features -- -D warnings

…ng in SQL parser. Closes #59

strip_sql_comments_and_trim and split_sql_statements already handle
backslash-escaped quotes (\') and SQL-standard doubled quotes ('') inside
string literals correctly — this was fixed as a side effect of the Safe
Mode multi-statement bypass fix (#54, commit 751393e), which rewrote the
in_string branch of both functions to consume the escape/doubled-quote
pair instead of treating the first quote as a closing quote.

Add regression tests for both functions plus enforce_safe_mode_precheck
covering the exact failure scenarios from #59: a query with an escaped
quote followed by `-- ` no longer has its trailing FROM clause eaten by
a fake comment, and a doubled-quote literal no longer leaks its content
as bare keywords or desynchronizes string tracking for the rest of the
query.
@ZhuchkaTriplesix
ZhuchkaTriplesix merged commit 93a9f4e into dev Sep 29, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant