[GitHub] [arrow-datafusion] matthewmturner commented on issue #1877: Improved schema and catalog support from SQL

[GitBox <gi...@apache.org>]

matthewmturner commented on issue #1877:
URL: https://github.com/apache/arrow-datafusion/issues/1877#issuecomment-1065916031


   Fortunately, we already have the ability to parse table refs into catalog, schema, and table with `TableReference::resolve(default_catalog, default_schema) -> ResolvedTableReference`.  I havent seen any issues with this yet.
   
   Definitely agree on maintaining current active catalog / schema.  From a pure sql / datafusion-cli perspective i was thinking of using the `\c` command like psql for connecting to a database / catalog.  Then for schema maybe support for the `SET` command with options like `search_path`.  Personally, im ok with those being follow on steps as im fine with using fully qualified names in queries for now.
   
   i believe postgres supports putting databases names, schemas, and tables in double quotes so i would think we could support something similar for resolving names with ".".
   
   In my current PR #1959 i thought i was actually quite close with adding `CREATE SCHEMA` support however im currently having an issue with getting the schema to register to the catalog.  Still need to figure that out.


-- 
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: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org