[CBRD-20174] Removed primary_key from MVCC_REEV_DATA #24
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
|
@andrei14vl |
ribram
pushed a commit
to ribram/cubrid
that referenced
this pull request
May 21, 2021
https://arniadb.atlassian.net/browse/SC-151 Compiler sees a mismatch of the order of the members in the class header and the order of initialization in the constructor.
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-20174
This field of MVCC_REEV_DATA was used incorrectly used after CBRD-20167 patch.
Also, in locator_delete_force_internal() the reevaluation data will be ignored when the object is already locked.