Separate out methods of the Catalog API that are used on the query side into a new trait `DatabaseSchemaProvider`. The new trait includes methods from the Catalog that get the underlying `DatabaseSchema` or interact with names/IDs. This will allow for a separate implementation of the Catalog for pro that only needs to hold a replicated/combined view in-memory of one or more catalogs without the need to do persistence that a write buffer's catalog needs to do. While in there I also switched the `QueryExecutorImpl::new` method to take an args struct to avoid the clippy lint. |
||
---|---|---|
.. | ||
src | ||
Cargo.toml |