findepi commented on issue #12144: URL: https://github.com/apache/datafusion/issues/12144#issuecomment-2326245954
> We could easily apply any query on the table function like This is a good point. Would we get similar benefits if we implemented `information_schema.routines` view (which SQL spec happens to define)? In any case, writing a full query to `information_schema.*` or to a table function, is a few key strokes. That's probably why we have `SHOW TABLES` statement even though the information is also available via `information_schema.tabes` and is more queryable there (one can select desired columns or apply filters). Summing up we have discussed these implementation options 1. `information_schema.routines` (as defined by the SQL spec) 2. `SHOW FUNCTIONS` (similar to `SHOW TABLES` and similar (but not identical) to some query engines like Snowflake, Trino/Presto or MySQL) 3. `datafusion_functions()` table function (similar to DuckDB's `duckdb_functions()`) Which one or which ones do we want to implement? How do arrive at this decision to make sure it's not questioned later by some project maintainer(s) that I failed to involve in the discussion? -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
