dssysolyatin commented on PR #4592: URL: https://github.com/apache/calcite/pull/4592#issuecomment-3447317381
I will create a Jira ticket when I’m more familiar with this topic. I still have a few questions in mind that I want to answer first. For example, in PostgreSQL, a row constructor creates an unnamed row type (which is basically a tuple). See the documentation: https://www.postgresql.org/docs/current/sql-expressions.html#SQL-SYNTAX-ROW-CONSTRUCTORS ``` WITH tbl(r) AS (VALUES(1)) SELECT ARRAY(SELECT ROW(r, r) FROM tbl LIMIT 1); ``` In this case, we don’t need the fields to be unique, we just need to relax the type checking so that field names are ignored. Could this logic also apply here with `SELECT r, r` ? How do other databases and the SQL standard define this behavior? (For example, in Snowflake there’s no such concept as an unnamed or anonymous row type, they only have objects, where both field names and their order matter). So, there are quite a few things to check before creating an issue -- 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]
