fix(oracle): retain DML targets and JSON type#156
Merged
Conversation
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
1 participant
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.
Summary
TargetAST support for Oracle UPDATE/DELETE DML targets, retaining table, inline-view, and TABLE(collection) targets.WITH CHECK OPTION CONSTRAINT ....JSONcolumn type while preserving JSON keyword identifier regressions.Test Plan
go test ./oracle/... -count=1go test ./... -count=1attempted; Oracle packages passed, but the full run fails in existing TiDB/MySQL container comparison tests and a TiDB catalog timeout unrelated to this Oracle change.