[CBRD-25708] Enable partition pruning when the partition key is a function expression and the WHERE clause uses the original column #5682
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
…ction expression and the WHERE clause uses the original column
…h the column type being compared, instead of relying on the function’s return type
…ED_EXPR containing ALL/SOME
Hamkua
commented
Dec 12, 2024
…key expression used in ALSM
…constant values in range partition table
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-25708
In CUBRID, when an expression is specified as the partition key, partition pruning can only occur if the same expression is compared to a constant value in the query's WHERE clause.
However, if the original column included in the expression is compared with a constant value in the condition, partition pruning does not work.
Therefore, this feature has been added to support partition pruning even when the original column in the expression is compared with a constant value in the WHERE clause.
When comparing the PRED_EXPR of type EVAL_TERM in where_pred and where_key, the types of the original column in the partition key expression and the constant value are checked for compatibility.
If they are compatible, the original column in the expression is replaced with the constant value, allowing the partition key value to be computed accordingly.