Allow Directus Cloud to change QUERY_LIMIT_DEFAULT #22179
Closed
JackMullinkosson
started this conversation in
Feature Requests
Replies: 2 comments
-
Per discussion on discord the |
Beta Was this translation helpful? Give feedback.
0 replies
-
For further information on what was incorrect about the flow that led to this issue, see this discussion. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Summary
Directus cloud users are not able to relate more than 100 items to a single item because of the QUERY_LIMIT_DEFAULT being set to 100. In the settings panel, users should have an option to change that. This feature would solve the issue described here: #22144
The potential solution suggested in the above issue is not viable because it does not account for users wishing to achieve this functionality through the app rather than through custom queries. I also reached out to cloud support to request they make the default limit higher for my specific use case but they denied my request.
Basic Example
No response
Motivation
Use case: You have a single venue related to hundreds of reservations. Or a single vendor related to hundreds of customers. In your database, you want to be able to see all of those customers or reservations and sort by the venue or vendors they are related to. You would also use this in Directus insights for example if you wanted to look through this type of data.
This is achievable if you are importing your data through custom queries, but the use case in which you are using the app, either through manual data entry or Directus flows, should be accounted for.
Detailed Design
Inside settings, a number input to allow users to change what their QUERY_LIMIT_DEFAULT would be.
Requirements List
Must Have:
Should Have:
Could Have:
Drawbacks
Will add another field to the settings panel which will end up making it harder to find what setting you're looking for
Alternatives
Perhaps it could be set on the collection itself
Adoption Strategy
Is already achievable through queries and self hosted so wouldn't break anything
Unresolved Questions
No response
Beta Was this translation helpful? Give feedback.
All reactions