#135: Allow queries with no particular sort order #127
+125
−6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add experimental
unordered()
API to all common query paths(
OrderExpression
+EntityExpressions
,TableQueryBuilder
,YqlOrderBy
).The experimental API sets no particular sort order for the query results.
That is, the results will be returned in an implementation-defined order
which is subject to change at any time, potentially even giving a different
ordering for repeated executions of the same query.
This is different from the
OrderExpression
beingnull
orYqlOrderBy
missing,because YOJ interprets these as "order query results by entity ID ascending"
to ensure maximum predictability of query results.
There might be some modest performance gains from removing an implicit
ORDER BY
clause from YOJ queries. The new experimental API allows users to take advantage
of these potential performance gains.