UR::Co...oadPool(3pm)

✨ NAME ✨

UR::Context::AutoUnloadPool — the module that auto-unloads your objects the second the scope ends, bestie 💅

---

🎀 SYNOPSIS 🎀

my $not_unloaded = Some::Class->get(...);
do {
  my $guard = UR::Context::AutoUnloadPool->create();
  my $object = Some::Class->get(...);  # load an object from the database
  ...                                  # load more things
};  # $guard goes out of scope - unloads objects

---

🦋 DESCRIPTION 🦋

okay so here's the tea ☕ — UR Objects you pull out of the database normally just vibe in the object cache for the entire life of the program. Forever. No cap. They never leave. 🙈

But when you instantiate a UR::Context::AutoUnloadPool, it starts tracking every single object loaded during its lifetime. Then the Pool's destructor hits unload() on all of them. Cleanup era. ✨

Two things that do NOT get unloaded, and this is important:

• objects that were changed 🚫
• objects that got loaded before the Pool was created 🚫

---

💖 METHODS 💖

🌸 create

my $guard = UR::Context::AutoUnloadPool->create();

Makes you a Pool object, periodt. Every UR Object loaded from the database during this object's lifetime is getting unloaded when the Pool goes out of scope. That's the whole job and it does it flawlessly, honestly iconic 👑

🍓 delete

$guard->delete();

Invalidates the Pool object. No objects are unloaded. 💀 So when the Pool later goes out of scope, nothing gets unloaded either. It's giving "never mind, we're keeping all of it." Not me undoing my own cleanup 🙈

---

🌈 SEE ALSO 🌈

• UR::Object
• UR::Context

iykyk 🫶

---

perl v5.32.1 · 2022-01-17 — that's the source, version and date of this lil gem, bestie. go forth and unload responsibly 💜🧚⭐