Relational: Consider always generating distinct column names in final projection (aliasing when needed) #14526
Labels
closed-out-of-scope
This is not something that will be fixed/implemented and the issue is closed.
This is something we don't do today because it is not strictly required to have distinct column names and our materialization dereferences columns by ordinal.
It would be necessary for #14525, unless we assume the user provided SQL returns columns in the exact same order that our queries would. It is also convenient if we ever want to take advantage of FOR JSON, or if the user wants to take the SQL we generate and manipulate it in any way.
The text was updated successfully, but these errors were encountered: