Skip to content

fix: preserve token boundaries in DDL parameter lists - #2857

Merged
manticore-projects merged 1 commit into
JSQLParser:masterfrom
minleejae:fix/ddl-parameter-token-boundaries-20261024
Oct 24, 2026
Merged

manticore-projects merged 1 commit into
JSQLParser:masterfrom
minleejae:fix/ddl-parameter-token-boundaries-20261024

Conversation

@minleejae

Copy link
Copy Markdown
Contributor

Opaque DDL parameter lists concatenate adjacent words and numbers: an Oracle vector index containing PARAMETERS (TYPE HNSW, NEIGHBORS 32) is rendered as PARAMETERS (TYPEHNSW,NEIGHBORS32). The result can still reparse while changing the parameter tokens.

Insert a separator between adjacent list items, preserving existing comma/equals formatting and quoted contents. Tests assert exact toString and StatementDeParser output for HNSW/IVF indexes and table storage options, plus literals, quoted names, booleans and numeric lists.

Syntax reference: Oracle CREATE VECTOR INDEX.

Validation: full Maven clean verify; Gradle check with Spotless ratcheted to upstream/master for this fork checkout; combined-change tests (414 tests) and the 238-input, three-configuration compatibility corpus, with no previously parsing input regressions.

@manticore-projects
manticore-projects merged commit 2927bad into JSQLParser:master Oct 24, 2026
10 checks passed
@manticore-projects

Copy link
Copy Markdown
Contributor

Thank you!

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.

2 participants