Skip to content

fix(security): preserve UTF-8 SQL parser offsets - #181

Merged
farhan-syah merged 1 commit into
mainfrom
fix-utf8-safe-sql-keyword-offsets
Jul 15, 2026
Merged

farhan-syah merged 1 commit into
mainfrom
fix-utf8-safe-sql-keyword-offsets

Conversation

@farhan-syah

Copy link
Copy Markdown
Member

Summary

  • derive SQL byte offsets only from the original input string
  • centralize ASCII case-insensitive forward, reverse, keyword, and literal-aware scanning
  • repair affected typed DDL, Control Plane, protocol, trigger, and graph parser paths
  • add expanding-Unicode regressions and persistent-connection protocol coverage

Validation

  • cargo nextest run -p nodedb-sql --no-fail-fast (728 passed)
  • cargo nextest run -p nodedb --lib --no-fail-fast (4299 passed)
  • focused pgwire RETURNING, SQL PREPARE, cursor, and native SET/SHOW integration regressions
  • cargo clippy --all-targets --all-features -- -D warnings
  • cargo fmt --all --check
  • git diff --check
  • exhaustive static security review: pass
  • regression coverage and layout review: pass

@farhan-syah
farhan-syah merged commit 8318ca4 into main Jul 15, 2026
@farhan-syah
farhan-syah deleted the fix-utf8-safe-sql-keyword-offsets branch July 15, 2026 13:33
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