We have a database called "Test" in our server. It happens often that a developer type "test" instead and try to use that database. In this case the server stops because he can not find the database files for "test".
This should not be happen, because someone could cause a stop of a production server this way.
- related to
-
SERVER-95530 Searching for conflicting DB names fails on non ASCII chars
-
- Open
-
-
SERVER-93173 CollectionRoutingInfoTargeter should not create database on read operations
-
- Backlog
-
-
SERVER-1443 something's not right with database name lettercase sensitivity in sharded setup
-
- Closed
-