[Fix] Throw BinderException for UNNEST expressions in WINDOW expressions #11247
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.
Fixes https://github.com/duckdblabs/duckdb-internal/issues/1450.
We allow subqueries in
WINDOW
expressions, so the following query returns an expected result.However, we do not allow
UNNEST
to be an expression outside a subquery inWINDOW
expressions. Previously, queries of the following nature would throw anInternalException
. This PR ensures that we now throw the expected binder exception.Relevant changes
inside_window
from theBaseSelectBinder
into theExpressionBinder
, to access it without type casting of binders in macro binding code-paths.ExpressionBinder
to (1) detectUNNEST
expressions (WindowContainsUnnest
), and to (2) bind aWINDOW
child expression with extra checks (BindWindowChild
).