MONGOC_BULKWRI...ECONCERNERRORS(3)

💅 MONGOC_BULKWRITEEXCEPTION_WRITECONCERNERRORS 💅

okay bestie, buckle up 💖 you're in libmongoc land, and this page is all about one very specific little function: mongoc_bulkwriteexception_writeconcernerrors. she's the one who tells you what the server side was mad about when your write concern settings weren't it. no cap.

---

✨ SYNOPSIS ✨

const bson_t *
mongoc_bulkwriteexception_writeconcernerrors (const mongoc_bulkwriteexception_t *self);

that's it. one function, one arg, one const bson_t * coming back at you 🫶

---

🦋 DESCRIPTION 🦋

she returns a BSON array of write concern errors. full stop. that array is the vibe check for "did the server side accept my write concern or not" 😭

like, here's what that array looks like in the wild:

[
   { "code" : 123, "message" : "foo", "details" : {  } },
   { "code" : 456, "message" : "bar", "details" : {  } }
]

see the pattern? each entry has a code, a message, and a details doc (sometimes empty, and that's fine, she's allowed to be lowkey shy 🙈).

and here's the important part, so don't skip it: if there are no write concern errors, you get back an empty array. not a NULL, not a maybe, an empty array. the way that a clean empty array is literally the most reassuring thing you'll see all day ✨

---

👑 AUTHOR 👑

MongoDB, Inc — icons only, periodt.

---

🌈 COPYRIGHT 🌈

2009-present, MongoDB, Inc. — yes she's been thriving since 2009, main character energy fr fr.

---

ok that's the whole page, no hidden bonus sections, no secret flags, nothing lurking. what you see is what you get 💜

libmongoc version 2.5.6, dated Oct 09, 2025 — mwah, love you, bye 💅🎀🦋💖