-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
Fully Compatible
-
CAR Team 2024-02-05, CAR Team 2024-02-19, CAR Team 2024-03-04
The following comment is present on several view related functions (create/dropView, iterateViews, etc):
"Caller must ensure corresponding database exists."
After SERVER-57250, we should explore removing this requirement, whether it just works or find out what's blocking it and consider what changes are required to make it work.
- depends on
-
SERVER-57250 CollectionCatalog should handle and own Views instead of ViewCatalog
- Closed
- is depended on by
-
SERVER-63679 Dissociate the in-memory view catalog logic from any in-memory database layer dependencies
- Backlog