Skip to content

feat: reuse table constraint grammar for PostgreSQL ALTER ADD - #2612

Merged
manticore-projects merged 1 commit into
JSQLParser:masterfrom
minleejae:feat/postgresql-shared-alter-constraints
Sep 12, 2026
Merged

manticore-projects merged 1 commit into
JSQLParser:masterfrom
minleejae:feat/postgresql-shared-alter-constraints

Conversation

@minleejae

Copy link
Copy Markdown
Contributor

In PostgreSQL mode, ALTER TABLE ADD cannot parse constraint forms already handled by CREATE TABLE, including EXCLUDE, CHECK ... NOT VALID and INITIALLY attributes. Reuse a shared table-constraint production with CREATE/ALTER-specific index-option boundaries, and centralize population of the legacy key accessors from structured indexes.

Regression tests cover named and unnamed constraints, PostgreSQL options and attributes, multiple actions, referenced-table discovery, legacy accessors and invalid tails. Existing non-PostgreSQL ALTER paths remain covered by the full suite.

Validation: Java 17 ./gradlew check passed, including the full test suite, a zero-choice-conflict grammar check and static analysis.

@manticore-projects
manticore-projects merged commit e4cf316 into JSQLParser:master Sep 12, 2026
10 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.

2 participants