-
Type: Bug
-
Resolution: Fixed
-
Priority: Minor - P4
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Fully Compatible
-
Execution Team 2023-02-20, Execution Team 2023-02-06
-
100
Currently dropping a nonexistent collection is an error (SERVER-41365). I think that if the user wants to drop the collection and it happens to already not exist, the outcome is successful. Thus dropping a nonexistent collection should do nothing and return success to the client.
- causes
-
VSCODE-461 Server 7.0 allows dropping nonexistent collections
- Open
- is duplicated by
-
SERVER-32550 Drop of a non-existing collection on mongod should have the same behavior as mongos
- Closed
- is related to
-
SERVER-60064 Make create command idempotent on mongod
- Closed
-
SERVER-73934 Remove commandWorkedOrFailedWithCode(NamespaceNotFound) from drop_collection.js when 7.0 is last stable release in multi version testing
- Closed
-
SERVER-41365 Improve unhelpful error "ns not found"
- Closed
-
NODE-5059 CRUD tests fail on latest because drop is not returning an NS not found error
- Closed
- related to
-
SERVER-90152 dropIndex() should be idempotent
- Blocked
-
SERVER-79358 Dropping a collection in a replicaset should result in a no-op for 6.0 and below
- Closed
-
SERVER-55145 Make dropping a nonexistent database a noop
- Closed
-
DRIVERS-2118 Create collection and database management specifications
- Backlog