Skip to content

feat: support Oracle DROP SYNONYM - #2855

Merged
manticore-projects merged 1 commit into
JSQLParser:masterfrom
minleejae:feat/oracle-drop-synonym-20261024
Oct 24, 2026
Merged

manticore-projects merged 1 commit into
JSQLParser:masterfrom
minleejae:feat/oracle-drop-synonym-20261024

Conversation

@minleejae

Copy link
Copy Markdown
Contributor

Oracle DROP SYNONYM statements currently fail, including the basic private-synonym form. Parse optional PUBLIC, IF EXISTS and FORCE, expose SYNONYM and public scope in the Drop model, and render Oracle FORCE separately from PostgreSQL WITH (FORCE).

Tests cover modifier combinations in default and Oracle modes, quoted and qualified names, model changes, statement boundaries, malformed clauses, and existing PostgreSQL force syntax. DROP lookahead is grouped in a nested helper to keep the generated parser instrumentable by JaCoCo within the JVM constant-pool limit.

Syntax reference: Oracle DROP SYNONYM.

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 d8b308d 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