MONGOC_READ_CONCERN_IS_DEFAULT(3)

📦
version 2.5.6 · 16 versions
, in epel 10

💖 MONGOC_READ_CONCERN_IS_DEFAULT(3) 💖

okay so like — welcome to the libmongoc manual, bestie 🫶 this one's a little function that tells you whether your read concern is still factory-fresh or if somebody's been messing with it. it's giving "vibe check for your read concern" and honestly? iconic.

✨ SYNOPSIS ✨

bool
mongoc_read_concern_is_default (mongoc_read_concern_t *read_concern);

that's the whole thing. one function, one argument, returns a bool. short and slay 💅

🎀 PARAMETERS 🎀

  • read_concern — a pointer to a mongoc_read_concern_t. yeah. that's the one you're checking. 🦋

🌸 DESCRIPTION 🌸

Returns true if read_concern has not been modified from the default. like, untouched. pristine. no notes. 🔥

so for example — say you never set a "readConcern" option in the MongoDB URI, and you also never called mongoc_client_set_read_concern(). in that case, mongoc_read_concern_is_default() returns true for the read concern you get back from mongoc_client_get_read_concern(). it's just sitting there being default, living its best life 😌✨

lowkey the whole point: this is how you find out if a read concern is still the plain ol' default or if something custom got applied to it. no cap. 🧚

👑 AUTHOR 👑

MongoDB, Inc — the authors, the icons, the moment. 💜

2009-present, MongoDB, Inc.

k that's the whole page, bestie — go forth and check your read concerns, fr fr 💖✨🎀

— with love from libmongoc version 2.5.6, dated Oct 09, 2026 🦋💅

📦 where this page comes from