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
{{ message }}
Repository navigation
SQL: WHERE-clauses don't support tables or schemas or catalogs #4872
Error: SqlLogicTest(query failed: DataFusion error: Schema error: No field named 'tables'.'table_schema'. Valid fields are 'information_schema.tables'.'table_catalog', 'information_schema.tables'.'table_schema', 'information_schema.tables'.'table_name', 'information_schema.tables'.'table_type'.
Since the relation here is information_schema.tables as a whole. Could try to make relation an Option<OwnedTableReference> instead. I'll take a shot at implementing this and exploring what this could look like.
Activity
Jefffrey commentedon Feb 5, 2023
Most relevant part seems to be here (where most errors are originating from):
https://github.com/apache/arrow-datafusion/blob/f8607c238d7c6dd1d33cf494722fa73466f73dd2/datafusion/sql/src/expr/identifier.rs#L73-L112
However there might be need to refactor
Column:https://github.com/apache/arrow-datafusion/blob/5dd5ffd5ea84d843b9ef34d0eaa9ac992618f6e2/datafusion/common/src/column.rs#L29-L34
Specifically with how it treats
relationas anOption<String>. The below SQL does work:Since the
relationhere isinformation_schema.tablesas a whole. Could try to makerelationanOption<OwnedTableReference>instead. I'll take a shot at implementing this and exploring what this could look like.