[CBRD-25317] The problem is that the Oracle-style LEFT OUTER JOIN is not rewritten as an INNER JOIN if there is a method call and host variables are used in the WHERE clause (#5292) #5992
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
…not rewritten as an INNER JOIN if there is a method call and host variables are used in the WHERE clause (CUBRID#5292) http://jira.cubrid.org/browse/CBRD-25317 After parsing, Oracle-style outer joins have the PT_EXPR_INFO_LEFT_OUTER or PT_EXPR_INFO_RIGHT_OUTER flag set on the PT_EXPR node where the join condition is specified. When converting Oracle-style outer joins to ANSI joins, these flags are not modified, so it appears that the join is changed to an outer join when pt_resolve_names() is called again after recompilation.
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-25317
backport #5292