fix(plan): add POW alias to functionIdRegister#24778
Open
ULookup wants to merge 1 commit into
Open
Conversation
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
heni02
approved these changes
Jun 2, 2026
aunjgr
approved these changes
Jun 2, 2026
Contributor
aunjgr
left a comment
There was a problem hiding this comment.
One-line fix — "pow": POW was missing from functionIdRegister while the POW = 149 constant and Power() execution function already existed. Unit test confirms getFunctionIdByName("pow") resolves; BVT covers uppercase/lowercase/float. LGTM.
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.
What type of PR is this?
Which issue(s) this PR fixes:
issue #24439
What this PR does / why we need it:
The
POW(x, y)MySQL alias forPOWER(x, y)was not recognized on 3.0-dev because the string"pow"was missing from thefunctionIdRegistermap infunction_id.go. The constantPOW = 149and thePower()execution function already existed — only the lookup registration was missing. This one-line fix adds"pow": POWto the register, making the function accessible through thePOW()name. A unit test validates the register lookup, and BVT test cases cover uppercase/lowercase/float POW calls.