MDEV-10426 ANY_VALUE function#5151
Draft
jaeheonshim wants to merge 14 commits into
Draft
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request implements the ANY_VALUE() function by adding it to the client commands, defining the Item_func_any_value class (inheriting from Item_func_coalesce), and registering it in the function registry. Feedback on the changes points out a critical issue: because Item_func_any_value inherits from Item_func_coalesce, it will still trigger ONLY_FULL_GROUP_BY errors unless check_cols_in_group_by() is overridden to return false directly.
gkodinov
added
the
External Contribution
… to non_agg_fields only if BOTH in_sum_func and in_any_value are false
…related subquery as long as it is aggregated
Under ONLY_FULL_GROUP_BY, a query that aggregated an outer column inside a subquery was wrongly rejected. This is fixed in Item_field::fix_outer_field by not appending the field to select->join->non_agg_fields when thd->lex->in_sum_func is not null. Furthermore, in Item_sum::check_sum_func, for all outer fields that are not aggregated at their SELECT_LEX's nest level, we append these fields to sel->join->non_agg_fields in order to ensure proper aggregation after the Item_sum's nest_level is known.
…g Item_sum_min_max
jaeheonshim
force-pushed
the
MDEV-10426-any-value
branch
from
c6f6e73 to
9525ad3
Compare
kjarir
added a commit
to kjarir/server
that referenced
this pull request
Jun 22, 2026
Per Daniel Black's reference to PR MariaDB#5151 (copy_or_same() fix for ANY_VALUE), investigated whether the same gap exists for our BIT_AND/BIT_OR/BIT_XOR binary mode aggregates. Finding: no bug exists. Item_sum_or/Item_sum_and/Item_sum_xor already have correct copy_or_same() implementations that clone via the Item_sum_bit copy constructor, which properly deep-copies m_str_value and m_binary_bit_counters for each rollup level's independent accumulator. Verified WITH ROLLUP produces mathematically correct results for binary mode BIT_OR/BIT_AND/BIT_XOR (manually cross-checked byte by byte against expected values). Added Section 16 as permanent regression coverage for this previously-untested combination.
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
5 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.
MDEV-10426: Add support for the MySQL
ANY_VALUE()function (SQL:2023 feature T626).