[#823] Allow RULE_EXEC_CONTEXT column access by GenQuery1 - #829
Merged
Conversation
korydraughn
reviewed
Aug 28, 2026
korydraughn
reviewed
Sep 2, 2026
korydraughn
left a comment
Contributor
There was a problem hiding this comment.
Looks good to me.
Is this ready for squashing?
Collaborator
Author
|
Ok, good the Github machinery finally rose in the right constellation and blessed this PR. The only exception is codacy's flagging of the cryptographic issue, which is ok as luckily the |
Collaborator
Author
think so. |
d-w-moore
force-pushed
the
823.m
branch
2 times, most recently
from
September 2, 2026 18:05
ef30c49 to
8205710
Compare
Collaborator
Author
|
Force-pushed after the squash so the commit message contains the explicit DB column being queried. |
Collaborator
Author
|
Ok, #'d |
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
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.
No description provided.