db.collection.drop()¶

Definition定义¶

db.collection.drop(<options>)¶

mongo Shell Method

This page documents the mongo shell method, and does not refer to the MongoDB Node.js driver (or any other driver) method. 本页记录了mongo shell方法，未提及MongoDB Nodejs驱动程序（或任何其他驱动程序）方法。For corresponding MongoDB driver API, refer to your specific MongoDB driver documentation instead.有关相应的MongoDB驱动程序API，请参阅特定的MongoDB驱动程序文档。

Removes a collection or view from the database. 从数据库中删除集合或视图。The method also removes any indexes associated with the dropped collection. 该方法还会删除与删除的集合关联的所有索引。The method provides a wrapper around the drop command.该方法为drop命令提供了一个包装器。

Note

For a sharded cluster, if you use db.collection.drop() and then create a new collection with the same name, you must either:对于分片集群，如果使用db.collection.drop()然后创建同名的新集合，必须：

• Flush the cached routing table on every mongos using flushRouterConfig.使用flushRouterConfig刷新每个mongos上的缓存路由表。
• Use db.collection.remove() to remove the existing documents and reuse the collection. 使用db.collection.remove()删除现有文档并重新使用集合。Use this approach to avoid flushing the cache.使用此方法可避免刷新缓存。

db.collection.drop() has the form:其形式如下：

Changed in version 4.0.在版本4.0中更改。db.collection.drop() accepts an options document.接受选项文档。

db.collection.drop( { writeConcern: <document> } )

db.collection.drop() takes an optional document with the following field:获取具有以下字段的可选文档：

Field字段

Description描述

writeConcern

Optional.可选。A document expressing the write concern of the db.collection.drop() operation. 表示write concern of the db.collection.drop()操作的写入关注点的文档。Omit to use the default write concern.忽略使用默认的写关注点。 When issued on a sharded cluster, mongos converts the write concern of the drop command and its helper db.collection.drop() to "majority".在分片集群上发出时，mongos将drop命令及其助手db.collection.drop()的写关注点转换为"majority"。 New in version 4.0.版本4.0中的新功能。

Returns:	true when successfully drops a collection.成功删除集合时为true。 false when collection to drop does not exist.如果要删除的集合不存在，则为false。

Behavior行为¶

• The db.collection.drop() method and drop command create an invalidate Event for any Change Streams opened on dropped collection.db.collection.drop()方法和drop命令为在删除的集合上打开的任何更改流创建一个invalidate事件。
• Starting in MongoDB 4.4, the db.collection.drop() method and drop command abort any in-progress index builds on the target collection before dropping the collection. 从MongoDB 4.4开始，db.collection.drop()方法和drop命令会在删除集合之前中止目标集合上任何正在生成的索引。Prior to MongoDB 4.4, attempting to drop a collection with in-progress index builds results in an error, and the collection is not dropped.在MongoDB 4.4之前，尝试删除具有进行中索引生成的集合会导致错误，并且不会删除该集合。

  For replica sets or shard replica sets, aborting an index on the primary does not simultaneously abort secondary index builds. 对于副本集或碎片副本集，中止主索引不会同时中止辅助索引生成。MongoDB attempts to abort the in-progress builds for the specified indexes on the primary and if successful creates an associated abort oplog entry. MongoDB尝试中止primary上指定索引的正在进行的构建，如果成功，则创建关联的abortoplog条目。Secondary members with replicated in-progress builds wait for a commit or abort oplog entry from the primary before either committing or aborting the index build.具有复制进行中生成的Secondary成员在提交或中止索引生成之前，会等待主成员的提交或中止oplog条目。

• Starting in MongoDB 4.0.2, dropping a collection deletes its associated zone/tag ranges.从MongoDB 4.0.2开始，删除集合将删除其关联的区域/标记范围。

Example示例¶

db.students.drop()

db.students.drop( { writeConcern: { w: "majority" } } )