MONGOC_CLIENT_SET_READ_CONCERN(3)

📦
version 2.5.6 · 16 versions
, in epel 10

💅 MONGOC_CLIENT_SET_READ_CONCERN(3) ✨

okay so bestie, this is a page straight out of libmongoc and it's about one tiny function that decides how your reads behave. buckle up, it's short and sweet 🍓

✨ SYNOPSIS ✨

void
mongoc_client_set_read_concern (mongoc_client_t *client,
                                const mongoc_read_concern_t *read_concern);

So this one sets the read concern for the client — that's it, that's the whole vibe. 🫶

Important though: it only affects future operations, collections, and databases inheriting from client. Like, it's not gonna time-travel backwards and fix stuff you already did, no cap. 🙈

The default read concern is MONGOC_READ_CONCERN_LEVEL_LOCAL — and honestly? that's the correct read concern for the great majority of applications. lowkey iconic default behavior, we love to see it. 👑

🚨 it is a programming error to call this function on a client from a mongoc_client_pool_t. Like, do not do it. For pooled clients, set the read concern with the MongoDB URI instead — that's the way, periodt. 💀

🎀 PARAMETERS 🎀

  • client: A mongoc_client_t. your main character client 💖
  • read_concern: A mongoc_read_concern_t. the read concern vibe you're assigning ✨

🌸 AUTHOR 🌸

MongoDB, Inc — the whole team, fr fr 🫶

2009-present, MongoDB, Inc. 💜

and that's the whole page bestie, tysm for reading 🎀✨🦋

signing off from libmongoc version 2.5.6, dated Oct 09, 2026 — mwah 💋

📦 where this page comes from