You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(2) p 9, sec 3.1.7. The "limit" Query Parameter
Allowed Values
The allowed values are unsigned integers. Note that passing zero
(0) as limit, SHOULD quickly return the empty set. This can be
useful to test if a query is valid without stressing the
datastore.
I'm not particularly keen on the text regarding passing 0 as the limit
being used to check whether the query is valid. This is feels like a
somewhat random capability check happening during the operation. It
probably means that a server would need to special case the handling for
the 0 limit to return a valid response but internally bypass the regular
query operation. Instead, I think that this text should probably make
the lower limit 1.
The text was updated successfully, but these errors were encountered:
(2) p 9, sec 3.1.7. The "limit" Query Parameter
Allowed Values
The allowed values are unsigned integers. Note that passing zero
(0) as limit, SHOULD quickly return the empty set. This can be
useful to test if a query is valid without stressing the
datastore.
I'm not particularly keen on the text regarding passing 0 as the limit
being used to check whether the query is valid. This is feels like a
somewhat random capability check happening during the operation. It
probably means that a server would need to special case the handling for
the 0 limit to return a valid response but internally bypass the regular
query operation. Instead, I think that this text should probably make
the lower limit 1.
The text was updated successfully, but these errors were encountered: