xiedeyantu commented on PR #4723: URL: https://github.com/apache/calcite/pull/4723#issuecomment-3714523124
@NobiGo I have checked these sql using pgsql, duckdb and calcite ``` select array[1,2,3]=any(array[1,2,3],array[4,2,3]),array[1,2,3]=any(array[1,3],array[4,2,3]); ``` it will throw an error in pgsql. ``` Query Error: operator does not exist: integer[] = integer ``` I've tried various methods of explicitly specifying the data type, but I haven't found a single SQL statement that works. ``` select array[1,2,3]=any(array[array[1,2,3],array[4,2,3]]),array[1,2,3]=any(array[array[1,3],array[4,2,3]]); ``` This sql can work well in duckdb and calcite. duckdb is also not supporting the following ``` select array[1,2,3]=any(array[1,2,3],array[4,2,3]),array[1,2,3]=any(array[1,3],array[4,2,3]); ``` Although this SQL can be executed in Calcite, the result seems inconsistent with what you provided. it will return following: EXPR$0, EXPR$1 false, false I don't know if we should support this format. I think we can merge this PR based on the current Jira version. If there's an issue with the SQL you mentioned, we can create a separate Jira instance to handle it. WDYT? -- 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]
