Repository navigation
feat: support Oracle TRUNCATE storage and log options - #2856
Merged
manticore-projects merged 1 commit intoOct 24, 2026
Merged
manticore-projects merged 1 commit into
manticore-projects merged 1 commit into
Conversation
Contributor
|
Thank you! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Oracle TRUNCATE TABLE statements with REUSE STORAGE, DROP [ALL] STORAGE or PRESERVE/PURGE MATERIALIZED VIEW LOG currently fail. Add separate structured storage and log options and render them in Oracle clause order before CASCADE, retaining the existing relation-target and PostgreSQL identity APIs.
Tests cover option combinations in default and Oracle modes, qualified and quoted names, model changes, malformed clauses and statement boundaries. Existing PostgreSQL TRUNCATE and LOCK target/identity tests remain covered. Relation-target construction, lookahead and option mapping live in a nested helper so the generated parser remains instrumentable by JaCoCo within the JVM constant-pool limit.
Syntax reference: Oracle TRUNCATE TABLE.
Validation: full Maven
clean verify; Gradlecheckwith Spotless ratcheted toupstream/masterfor this fork checkout; combined-change tests (414 tests) and the 238-input, three-configuration compatibility corpus, with no previously parsing input regressions.