HCK-13007: rename tables and views #199
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
taras-dubyk
reviewed
Oct 14, 2025
forward_engineering/alterScript/alterScriptHelpers/alterViewHelper.js
Outdated
Show resolved
Hide resolved
forward_engineering/alterScript/alterScriptHelpers/entityHelpers/nameHelper.js
Outdated
Show resolved
Hide resolved
|
taras-dubyk
approved these changes
Oct 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Content
Technical details
RENAMEonly works on objects in the current schema. So when there are name changes in multiple schemas we will use alterSession script to properly address the correct view. It shouldn't affect other statements as in most cases we use absolute paths to objects (i.e.schema.table.column)