bobtins commented on issue #1877: URL: https://github.com/apache/arrow-datafusion/issues/1877#issuecomment-1065776134
Hi, noticed this issue and just wanted to put my two cents in. <soapbox> The tl;dr is that most of the time you don't need these added levels; at most maybe add schema. I've worked with a data analysis tool that was cross-database in nature, and I noticed that catalogs and schemas mean different things for each DB impl, and most of the time I never had to deal with "catalog". If for PostgreSQL it's the same as "database", I'm not sure why you need "create catalog" if you have "create database". The sample output you are showing looks like it's from "information_schema" which is just a generic metadata standard that tries to be one size fits all; as such, it has things that are only used in some DBs. That said, it's kind of counterintuitive that a "." in a table name is a legal character, as you demonstrate. Personally, I can get by without either schema or catalog, but YMMV... </soapbox> -- 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]
