[CBRD-25289] Backport from develop to 11.3 - When using the --split-schema-files option in unloaddb, the unique index must be separated from the dbname_schema_class file. #5085
Conversation
This file contains 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
…the unique index must be separated from the dbname_schema_class file. (CUBRID#5083) http://jira.cubrid.org/browse/CBRD-25289 It is necessary to separate the Unique Index from the dbname_schema_class file. Unloaddb can use the --split-schema-files option to separate Unique indexes, and the separated Unique indexes are recorded in dbname_schema_uk, and dbname_schema_uk must be recorded in dbname_schema_info. Also, dbname_schema_info containing dbname_schema_uk must be able to be loaded from loaddb.
kisoo-han
approved these changes
Apr 5, 2024
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.
http://jira.cubrid.org/browse/CBRD-25289