comphead commented on issue #3990: URL: https://github.com/apache/arrow-datafusion/issues/3990#issuecomment-1370146262
> I tried making datafusion consistent with postgres in this regard a while back, and I ran into a problem. In the PG example above, the result of the query has two columns named "sum". DataFusion does not allow a result set to have two columns with the same name. Perhaps we need to allow this and only throw an error if attempting to reference a column that is ambiguous. Yes, DF checks the column uniqueness in logical plan builder in `validate_unique_names`. I agree we can try to move the check to later phase when outer query references an ambiguous column -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
