Have you thought about solving the problem from a different direction? Providing a read-only, sanitized clone of the database that can be accessed outside of the core application code?
Seems like that could kill more birds with the same stone?
Seems like that could kill more birds with the same stone?
We've peeked at Snaplet in the past, and :heart: your design aesthetic
As an aside: Not exactly sure why the parent is getting down voted.
I'm not saying that your post was such a hijack, but it's difficult to interpret these things accurately, so any post of this kind will always land on a spectrum of responses.