MONGOC_URI_GET_READ_CONCERN(3)

✨ MONGOC_URI_GET_READ_CONCERN(3) ✨

okay bestie, welcome to libmongoc — this one's a lil function from the MongoDB C driver and it's honestly so chill. it's giving "just peek, don't touch" energy, and you're gonna get it immediately, i promise 🫶

---

🌸 SYNOPSIS 🌸

const mongoc_read_concern_t *
mongoc_uri_get_read_concern (const mongoc_uri_t *uri);

look at her. two lines. iconic. 💅

---

🎀 PARAMETERS 🎀

• uri — a mongoc_uri_t. that's it. that's the whole parameter list. one (1) uri, handing over its read concern vibes ✨

---

🦋 DESCRIPTION 🦋

so basically this function fetches a read concern that is owned by the URI instance — meaning like, the URI is the main character here and it keeps custody of the thing, okay? you're just visiting 👑

and this read concern? it's configured based on URI parameters. so whatever you baked into the URI, that's what you're getting back. no cap. 🔥

lowkey important: the read concern belongs to the URI. it's not yours to keep. remember that for the next section, bestie 😭

---

⭐ RETURNS ⭐

returns a mongoc_read_concern_t that should not be modified or freed if a read concern is provided to uri — otherwise NULL.

so real talk: if you get one back, do not modify it, do not free it. hands off. it's not yours, it's the URI's. the way that ownership rule is non-negotiable fr fr 💀

and if uri wasn't given a read concern? you get NULL. that's the whole vibe check. 🫶

---

👑 AUTHOR 👑

MongoDB, Inc

---

🌈 COPYRIGHT 🌈

2009-present, MongoDB, Inc.

---

and that's the page, bestie!! go forth and don't free that read concern 💖

🌸✨ this has been libmongoc documentation, version 2.5.6, dated Oct 09, 2026 — catch you in the next manpage, mwah 🎀🦋💜