Hi folks,
I'd like to propose a change to our existing GetApplicablePolicies API
endpoint (GET /v1/{prefix}/applicable-policies) and gather your feedback.
Currently, this endpoint retrieves policies applicable to a given target
(e.g., table or view), including those inherited from parent entities
I'm generally a +1 on using JSONB within Postgres.
However I am in agreement with Dennis that we should avoid his item (2)
above. If the application will need to load entities by some attributes A,
B, and C then we should create methods loadEntityByA(a: A),
loadEntityByB(b: B), and loadEntityByC(c