Is your feature request related to a problem? Please describe.
Since we have relations it can be necessary to fetch only certain rows of a table, while it isn't possible to create views for that.
Example shopping cart: Imagine you have a shopping cart connected to a user, but multiple products that can be in the shopping cart (1-n relation in my example, would also be valid for n-m). The product rows define into which shopping cart row they belong. So: When I know the shopping cart, I could fetch the specific rows belonging there.
Currently, rows cannot be filtered server side and need to be filtered by the calling application, which will be very slow for big tables.
Describe the solution you'd like
Be able to add filters to rows/views GET requests, based on normal column values but also based on creator/creation date etc.
Describe alternatives you've considered
Filtering client side, which is really slow for big tables.
Additional context
No response
Is your feature request related to a problem? Please describe.
Since we have relations it can be necessary to fetch only certain rows of a table, while it isn't possible to create views for that.
Example shopping cart: Imagine you have a shopping cart connected to a user, but multiple products that can be in the shopping cart (1-n relation in my example, would also be valid for n-m). The product rows define into which shopping cart row they belong. So: When I know the shopping cart, I could fetch the specific rows belonging there.
Currently, rows cannot be filtered server side and need to be filtered by the calling application, which will be very slow for big tables.
Describe the solution you'd like
Be able to add filters to rows/views GET requests, based on normal column values but also based on creator/creation date etc.
Describe alternatives you've considered
Filtering client side, which is really slow for big tables.
Additional context
No response