---
name: "mongoc_collection_write_command_with_opts"
section: "3"
platform: "linux"
package: "libmongoc-doc"
version: "1.30.4-1+deb13u3"
release: "Debian 13 (Trixie)"
platforms: ["linux"]
url: "https://new.carta.tech/mongoc_collection_write_command_with_opts"
---

# mongoc\_collection\_write\_command\_with\_opts(3)

## SYNOPSIS

```
bool
mongoc_collection_write_command_with_opts (mongoc_collection_t *collection,
                                           const bson_t *command,
                                           const bson_t *opts,
                                           bson_t *reply,
                                           bson_error_t *error);
```

Execute a command on the server, applying logic that is specific to commands that write, and taking the MongoDB server version into account. To send a raw command to the server without any of this logic, use *mongoc\_collection\_command\_simple()*.

Use this function for commands that write such as "drop" or "createRole" (but not for "insert", "update", or "delete", see *Basic Write Operations*). Write concern and collation can be overridden by various sources. In a transaction, read concern and write concern are prohibited in **opts**. The highest-priority sources for these options are listed first in the following table. The write concern is omitted for MongoDB before 3.4.

| | |
| --- | --- |
| Write Concern | Collation |
| **opts** | **opts** |
| Transaction |  |
| **collection** |  |

*See the example for transactions* and for *the "distinct" command with opts*.

**reply** is always initialized, and must be freed with *bson\_destroy()*.

## PARAMETERS

- •

  **collection**: A *mongoc\_collection\_t*.

- •

  **command**: A *bson\_t* containing the command specification.

- •

  **opts**: A *bson\_t* containing additional options.

- •

  **reply**: A maybe-**NULL** pointer to *overwritable storage* for a *bson\_t* to contain the results.

- •

  **error**: An optional location for a *bson\_error\_t* or **NULL**.

**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 to **opts**. See the example code for *mongoc\_client\_write\_command\_with\_opts()*.

- •

  **sessionId**: First, construct a *mongoc\_client\_session\_t* with *mongoc\_client\_start\_session()*. You can begin a transaction with *mongoc\_client\_session\_start\_transaction()*, optionally with a *mongoc\_transaction\_opt\_t* that overrides the options inherited from **collection**, and use *mongoc\_client\_session\_append()* to add the session to **opts**. 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.

Consult *the MongoDB Manual entry on Database Commands* for each command's arguments.

## ERRORS

Errors are propagated via the **error** parameter.

## RETURNS

Returns **true** if successful. Returns **false** and sets **error** if there are invalid arguments or a server or network error.

A write concern timeout or write concern error is considered a failure.

## BASIC WRITE OPERATIONS

Do not use this function to call the basic write commands "insert", "update", and "delete". Those commands require special logic not implemented in **mongoc\_collection\_write\_command\_with\_opts**. For basic write operations use CRUD functions such as *mongoc\_collection\_insert\_one()* and the others described in *the CRUD tutorial*, or use the *Bulk API*.

## EXAMPLE

See the example code for *mongoc\_client\_read\_command\_with\_opts()*.

## AUTHOR

MongoDB, Inc

## COPYRIGHT

2009-present, MongoDB, Inc.