- 
    Type:Improvement 
- 
    Resolution: Unresolved
- 
    Priority:Major - P3 
- 
    None
- 
    Affects Version/s: None
- 
    Component/s: None
- 
        Catalog and Routing
- 
        3
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
We should continue to support helper utilities wherein higher layers than the catalog may act on a particular database's views. However, the view catalog logic should not be in-memory component dependencies on any database components.
SERVER-63661 is related to this task in that SERVER-63661 explores removing one of the known database dependencies. SERVER-63661 is a small piece of this ticket's task.
- depends on
- 
                    SERVER-63661 Explore removal of "Caller must ensure corresponding database exists." requirement on view catalog changes -         
- Closed
 
-         
- is related to
- 
                    SERVER-63683 Explore a path to move the view catalog's persisted state away from being database oriented -         
- Backlog
 
-         
- 
                    SERVER-63788 Clarify write semantics of various CollectionCatalog methods -         
- Backlog
 
-