This topic discusses the global sort order of records.
Once the records have been added to the data
store, the Oracle Endeca Server maintains data files for the records in memory.
The following rules apply to how the records are sorted in the results returned
by the Oracle Endeca Server in response to queries:
- Records are sorted according
to the sort order that you specified, if any.
- Even if you specified a
sort order, it may not have uniquely determined the resulting order of records
— this usually happens when some records only differ in attributes that were
not included in the sort specification. In such cases, the Dgraph process
tie-breaks the sorting results at random.
- Subsequent requests with the
same query will result in the same order (the tie-break is consistent) unless
you have modified the records in any way between requests. For example, the
order will change if you delete any of the records and add them to the data
store again, even if they are identical.
Note that when a sorted record result list is requested, string values
will be sorted case-insensitively, with ties broken with a case-sensitive
comparison (upper-cased letters will rank above lower-cased letters). For
example, for the six records
A,
B,
C,
a,
b, and
c, the resulting sort order will be:
A
a
B
b
C
c