You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The degree check is generally implemented wrong / too early.
We're currently checking for the correct degree of a SELECT subquery in a set operation already when the select list has been parsed. But at this point, we can't resolve asterisks yet, so we don't know the degree, which is one of the reasons why this special case here doesn't parse.
We can check things once we have parsed the entire set operation subquery, prior to assembling the subqueries in a combined query.
I'll keep the old degree check for now to double-check. Removing it breaks a few test assertions, e.g. when this isn't expected to parse: (a, b) = any (select 1)
The following valid SQL query fails to parse:
The error is:
We must not check for column size correctness in set operations when we don't know the row size of one of the subqueries
The text was updated successfully, but these errors were encountered: