Membership FilterCheck
Hello lovely people 
I’ve been working on a custom SpaceMemberFilter policy check (using
I took inspiration from
I attached the whole code, It works, but I’m worried about:
- Performance: I have to precompute the actor’s valid space IDs in a separate query (get_actor_space_ids/2) and then use an in expression against them. It feels clunky and potentially expensive for actors with many memberships.
- Elegance: I tried several approaches with expr/exists to avoid the extra query and push everything into one correlated subquery, but always hit Data layer does not support unrelated exists expressions.
So my question is:
Is there a cleaner or more idiomatic way in Ash to implement this check (ideally using exists/2 or similar) without doing the extra query to get all space IDs first?
Thanks in advance
I’ve been working on a custom SpaceMemberFilter policy check (using
Ash.Policy.FilterCheckI took inspiration from
Ash.Policy.Check.RelatesToActorViaspace_idI attached the whole code, It works, but I’m worried about:
- Performance: I have to precompute the actor’s valid space IDs in a separate query (get_actor_space_ids/2) and then use an in expression against them. It feels clunky and potentially expensive for actors with many memberships.
- Elegance: I tried several approaches with expr/exists to avoid the extra query and push everything into one correlated subquery, but always hit Data layer does not support unrelated exists expressions.
So my question is:
Is there a cleaner or more idiomatic way in Ash to implement this check (ideally using exists/2 or similar) without doing the extra query to get all space IDs first?
Thanks in advance
space_member_filter.ex3.65KB
The Elixir backend framework for unparalleled productivity. Declarative tools that let you stop wasting time. Use with Phoenix LiveView or build APIs in minutes for your front-end of choice.
2,193Members
Resources
Similar Threads
Was this page helpful?
