Augment queries - add an additional filter

[d0ivanov]

The application I'm working on is multi-tenant. The approach to tenant data isolation that all tables get an additional "tenant id" column. This results in pretty much every query having a WHERE clause like "...AND tenant_id = ".
I've been evaluating the possibility of customizing query creation and processing so that this additional clause gets appended "automagically" based on the current security context.
So far I've found this issue in Spring Data JPA, but it doesn't seem like there's any active development on it.
So I was wondering what would be your advice on the best approach right now to appending an additional filter to every query.

[mp911de]

Thanks for bringing this up. Query augmentation spans a large surface as that is something to consider for derived queries as well. We first need a proper design before we can proceed in any direction. Right now we don't have much bandwidth for that issue.

[d0ivanov]

I see, thank you for your response!
Granted it would be more of a patch - would you be willing to accept a change to make R2dbcQueryCreator a public class and also add a protected method in PartTreeR2dbcQuery which provides R2dbcQueryCreator instances ?

[mp911de]

R2dbcQueryCreator and friends are protected as we do not want to leak implementation details outside of that package. Making things public leads to usage and subclassing and that removes the ability on our side to update implementation details without breaking application code.

[jwmaher]

@mp911de With the current feature set how would you recommend this be accomplished? I have a similar requirement where i would like to inspect each query before it is executed