[CBRD-25801] Problems that occur when a hidden column is generated due to ORDER BY clause in a subquery #5780
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
youngjinj
reviewed
Jan 9, 2025
Co-authored-by: Joo Youngjin <[email protected]>
…nto CBRD-25801
youngjinj
approved these changes
Jan 9, 2025
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-25801
In CBRD-24181, when optimizing the select list of a subquery, a column in ORDER BY is added. At that time, a hidden column property is added, and the query that has already been rewritten in qo_rewrite_hidden_col_as_derived() is unnessarary rewritten twice, causing an issue. Fix to remove the hidden property if the existing select list does not have it.