[discussion] Improvements to data filtering

[olicooper]

I have spent a week working on a proof-of-concept demo to see if we could intercept database queries to apply ABP concepts to them before they are executed. I'd like to open this up to a discussion about how useful this is for people and how this could be used in ABP to make it more flexible. This need for flexibility has been mentioned before. It could be provided as part of the core ABP implementation or possibly included as a plugin (I have not investigated this yet).

My demo intercepts queries to apply IDataFilters without relying on Entity Framework's Global Query Filters which offers limited/restricted functionality. There are bugs and the code isn't clean because its a prototype so you'll probably be able to break it - I don't mind :)

My motivation for this is due to a few issues I have seen recently:

• Data filters cause database index scan instead of index seek #6680 - Queries can't be indexed by database providers due to the the dynamic parameters IsSoftDeleteFilterEnabled and IsMultiTenantFilterEnabled in AbpDbContext.
• A Bug With Soft Deleted related entities #7482 / EF Core index and soft delete entity. #1181 - Filters can't be disabled for navigation items
• Can implement dynamic data filtering? #5650 / filtering limitations - Filtering can't be customised

The wider community also wants the filters to be more flexible too:

• Add support for ignoring query filter on Include dotnet/efcore#21093
• Including entity with a query filter can cause not loading the root entity dotnet/efcore#11691
• Named query filters dotnet/efcore#8576

I have written an extensive readme to explain the project if you need more info.

Here is the demo: https://github.com/olicooper/abp-queryfilter-test

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.