Yeah. I'm imagining e.g. a full database schema at my disposal in the ORM layer, but with only the handful of rows relevant to the logged-in user.
Could be useful in many read-heavy scenarios, and would make a default way that skips DB fetches.
Could be useful in many read-heavy scenarios, and would make a default way that skips DB fetches.
I guess you could use to recreate the DB at the ORM level since you know the schema as well. But I still like this idea living at the database layer and not an extra layer of abstraction on top of it.