-
Notifications
You must be signed in to change notification settings - Fork 46
Description
Problem to Solve
Currently, Studio silently applies a limit
to all queries that do not already have a limit
, with the number of results configured in settings and a default value of 1000. This can lead to unexpected behaviour whereby a user does not realise their query is being limited and so processes the results without consideration of potential further results.
Current Workaround
Figure out that there's a default limit applied in settings.
Proposed Solution
Display a warning-level dialogue to the user when a query returns a number of results equal to the default limit if the query was not explicitly supplied with a limit
. With the current protocol, It is not possible to distinguish the edge case where the query has returned a number of results exactly equal to the limit, so the message should be phrased along the lines of:
The number of results for this query may exceed those returned, as the default query limit was reached. The default limit can be configured in Settings / Query Runner / Default Match Query Limit.
Stating how the setting can be changed is vital for UX.