MONGOC_WRITE_C...RN_SET_JOURNAL(3)

📦
version 2.5.6 · 16 versions
, in epel 10

okay bestie, welcome to MONGOC_WRITE_C...RN_SET_JOURNAL(3) from the libmongoc manual ☕✨ it’s a tiny setter with big “did you journal this?” energy, and yes, we’re gonna get into it.

✨ SYNOPSIS ✨

          void
          mongoc_write_concern_set_journal (mongoc_write_concern_t *write_concern,
                                            bool journal);

it returns void, so it’s a “do the thing” function, not a “hand you back a value” function 🎀

🎀 PARAMETERS 🎀

  • write_concern — a mongoc_write_concern_t. that’s the write concern struct you’re updating, bestie 💅
  • journal — a boolean. yes/no, on/off, journal-or-not vibes 🦋

💖 DESCRIPTION 💖

this function sets whether the write must have been journaled before it can indicate success. like, “did this actually get journaled?” — that’s the check. no cap 💖

beginning in version 1.9.0, this function can now alter the write concern after it has been used in an operation. glow-up behavior, honestly ✨

previously, using the struct with an operation would mark it as “frozen” 🧊 and calling this function would log a warning instead instead of altering the write concern. (yes, “instead instead” — that’s what the page says, and I respect the drama 😭)

important vibe check: the old frozen-struct situation meant your call wasn’t actually changing the write concern; it was just logging a warning. version 1.9.0 fixed that. periodt. 💅

👑 AUTHOR 👑

MongoDB, Inc

2009-present, MongoDB, Inc.

k bye bestie, mwah 🫶 this page is from the libmongoc source, version 2.5.6, dated Oct 09, 202… — the footer’s last year digit got cut off by the header, not me being mysterious 🎀

📦 where this page comes from