mongoc_collection_drop_with_opts()¶
Synopsis¶
bool
mongoc_collection_drop_with_opts (mongoc_collection_t *collection,
bson_t *opts,
bson_error_t *error);
Parameters¶
collection
: A mongoc_collection_t.error
: An optional location for a bson_error_t orNULL
.
opts
may be NULL or a BSON document with additional command options:
writeConcern
: Construct a mongoc_write_concern_t and use mongoc_write_concern_append() to add the write concern toopts
. See the example code for mongoc_client_write_command_with_opts().sessionId
: Construct a mongoc_client_session_t with mongoc_client_start_session() and use mongoc_client_session_append() to add the session toopts
. See the example code for mongoc_client_session_t.collation
: Configure textual comparisons. See Setting Collation Order, and the MongoDB Manual entry on Collation. Collation requires MongoDB 3.2 or later, otherwise an error is returned.serverId
: To target a specific server, include an int32 “serverId” field. Obtain the id by calling mongoc_client_select_server(), then mongoc_server_description_id() on its return value.
Description¶
This function requests that a collection
be dropped, including all indexes associated with the collection
.
If no write concern is provided in opts
, the collection’s write concern is used.
Errors¶
Errors are propagated via the error
parameter.
Returns¶
Returns true if the collection was successfully dropped. Returns false
and sets error
if there are invalid arguments or a server or network error.