- 
    Type:Task 
- 
    Resolution: Won't Do
- 
    Priority:Major - P3 
- 
    None
- 
    Affects Version/s: None
- 
    Component/s: None
- 
        Service Arch
- 
        2
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
ScopedBaseDDLLock private constructor third parameter is called StringData resName which stands for Resource Name.
This resource name is passed and stored under _resourceName which is then ONLY used to as a second parameter of lock and unlock of the _lockManager.
For these two methods, the third parameter which accepts a StringData is marked as ns which makes me think this could accept a NamespaceString.
It's then used in the DDLLockManager::_registerResourceName and passed to a DDLResourceName.
- related to
- 
                    SERVER-80549 Make DatabaseNameUtil::de/serialize no longer use default serialization context -         
- Closed
 
-