Repository navigation
Conversation
spetrunia
force-pushed
the
13.2-MDEV-40553-review-input
branch
from
October 8, 2026 08:06
5949579 to
8687b0e
Compare
I_S.OPTIMIZER_CONTEXT has this statement: set @opt_context='CONTEXT'; -- denote CONTEXT-STMT And opt_context_save_in_var.inc just took the CONTEXT and put it in a variable: SET @opt_context= (select REGEXP_SUBSTR(...) from i_s.optimizer_context); This ignored the fact that the "CONTEXT" is escaped for the SQL parser. Fix this by extracting the entire CONTEXT-STMT and running it.
spetrunia
force-pushed
the
13.2-MDEV-40553-review-input
branch
from
October 8, 2026 08:19
8687b0e to
67a5f30
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I_S.OPTIMIZER_CONTEXT has this statement:
set @opt_context='CONTEXT'; -- denote CONTEXT-STMT
And opt_context_save_in_var.inc just took the CONTEXT and put it in a variable:
SET @opt_context= (select REGEXP_SUBSTR(...) from i_s.optimizer_context);
This ignored the fact that the "CONTEXT" is escaped for the SQL parser.
Fix this by extracting the entire CONTEXT-STMT and running it.