MONGOC_COLLEC...DIFY_WITH_OPTS(3)

okay bestie, this is the mongoc_collection_find_and_modify_with_opts() page from libmongoc — yes, the header is out here doing MONGOC_COLLEC...DIFY_WITH_OPTS(3) and it's iconic 💅✨

✨ SYNOPSIS ✨

here's the signature in all its glory, copy it exactly fr fr:

bool
mongoc_collection_find_and_modify_with_opts (
   mongoc_collection_t *collection,
   const bson_t *query,
   const mongoc_find_and_modify_opts_t *opts,
   bson_t *reply,
   bson_error_t *error);

🫶 PARAMETERS 🫶

• collection — a mongoc_collection_t, aka the collection in question 💖
• query — a bson_t containing the query to locate target document(s) 🔍
• opts — a find and modify options. Must not be NULL. periodt.
• 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 🫶

🌸 DESCRIPTION 🌸

Update and return an object. That's the whole assignment, and it ate 💅

reply is always initialized, and it must be freed with bson_destroy() — no skipping that, bestie.

If an unacknowledged write concern is set (through mongoc_find_and_modify_opts_append()), the output reply is always an empty document. Lowkey crucial.

On success, the output reply contains the full server reply to the findAndModify command. For the expected server reply, see the MongoDB Manual page for findAndModify — that's the reference, fr fr.

😭 ERRORS 😭

Errors are propagated via the error parameter. That's the tea ☕

🔥 RETURNS 🔥

Returns true if successful. Returns false and sets error if there are invalid arguments or a server or network error — vibe check failed, basically.

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

🦋 EXAMPLE 🦋

See the example code for mongoc_find_and_modify_opts_t. Go look, bestie 👀

👑 AUTHOR 👑

MongoDB, Inc

🎀 COPYRIGHT 🎀

2009-present, MongoDB, Inc.

kiss kiss, this page is from libmongoc version 2.5.6, dated Oct 09, 2026 — stay iconic, and may your reply always be initialized 💖✨