In #8655 we deprecated the non-hierarchical usage of schema everywhere (hopefully).
In an effort to make that as smooth as possible for users, we settled on a pattern of allowing passing in either a tuple of strings or a dotted string path "catalog.database" as the argument to the database kwarg.
Once schema is removed, we should also add a catalog kwarg to allow users to specify table hierarchy in a slightly more programmatic way. There is some bookkeeping around how to handle combinations of arguments to catalog and database, but we've effectively already written it all, just for database and schema.
In #8655 we deprecated the non-hierarchical usage of
schema
everywhere (hopefully).In an effort to make that as smooth as possible for users, we settled on a pattern of allowing passing in either a tuple of strings or a dotted string path
"catalog.database"
as the argument to thedatabase
kwarg.Once
schema
is removed, we should also add acatalog
kwarg to allow users to specify table hierarchy in a slightly more programmatic way. There is some bookkeeping around how to handle combinations of arguments tocatalog
anddatabase
, but we've effectively already written it all, just fordatabase
andschema
.xref 8867