So here is where I am headed with this concept of user definable multi-level filter logic. Just interested in feedback.
- UI provides logic to build filters for predefined fields and save these filters in the database for the user.
- User can then make a request to use a set of filters with conjunction logic.
- I am writing a @custom script with a lambda function to accept variables with tells the script which filters to use.
- Then it makes a request back to dgraph to get those filter values.
- From these filter values it actually generate a DQL (or whatever we are calling it now) and
- Then sends that to dgrqph to
- Return a list of uids that fully appease the filters.
- These uids are returned to the UI and then
- Used to get the actual data to display and paginate.
This solves a few problems.
- Paginating with cascade
- Many queries required for deep nested logic conjucted together.