MDEV-24943: Implement FILTER clause support for aggregate functions #4439
+1,247
−37
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.
Description
Aggregates lacked the SQL-standard
FILTERclause, forcing CASE-based workarounds that reduced readability.This update introduces the ability to specify a
FILTERclause for aggregate functions, allowing for more granular control over which rows are included in the aggregation. Also, improves standards compliance and makes queries clearer and more readable.The
<condition>may contain any expression allowed in regularWHEREclauses, except subqueries, window functions, and outer references.Example:
How can this PR be tested?
Running the Test Suite
Validating CASE vs FILTER Equivalence
Use the
compare.pyscript to verify CASE and FILTER produce identical results:Expected Result File Format:
The script expects result files with this structure:
The script identifies test headers (
# Test N: Description), CASE/FILTER markers (# 1. CASE version/# 2. FILTER version), and compares the data rows that follow each marker.Basing the PR against the correct MariaDB version
mainbranch.PR quality check