UR::Da...pIndex(3pm)

💖 UR::DataSource::RDBMS::BitmapIndex 💖

okay bestie, so this is the UR::DataSource::RDBMS::BitmapIndex page from the User Contributed Perl Documentation (that's the 3pm manual section, for all my perl module girlies 🫶). it's short, it's sweet, it's giving metadata, and we're gonna get into it. no skimming, no scrolling past, we read the whole thing together 💅

---

✨ NAME ✨

UR::DataSource::RDBMS::BitmapIndex — metadata about a data source's bitmap indexes 🦋

like. that's the whole name. that's the whole vibe. it does exactly what it says on the tin, no cap.

---

🌸 DESCRIPTION 🌸

so, this class? it represents instances of bitmap indexes in a data source. that's the whole main character job description, periodt. 🎀

these lil guys aren't just floating around doing whatever, bestie — they are maintained by ur update classes and they get stored in the namespace's MetaDB. so if you were wondering where they live, that's where. the MetaDB. their little home. 💖

now here's the part where it gets real — the existence of bitmap indexes in a datasource affects SQL generation during a Context commit. lowkey huge, highkey important, iykyk. 🧚

and then the specific tea: Oracle's implementation requires that a table covered by a bitmap index be locked while it is being updated. locked!! while updating!! so yeah, the mere presence of these indexes is not a neutral thing, it's got consequences for how the SQL comes out. not me being dramatic, that's just literally what the page says 😭🔥

so like — don't forget: bitmap indexes existing = SQL generation during a Context commit is affected, and on Oracle that means locking the table while it's being updated. iconic behavior, but behavior nonetheless 👑

---

and that's the whole page, bestie!! short king. we ate. 💅✨

this was perl v5.32.1, dated 2022-01-17 — mwah, love that for us, bye bye now 🎀🌈💜