@@ -60,13 +60,10 @@ class StructuredQuery(proto.Message):
6060 order_by (MutableSequence[google.cloud.firestore_v1.types.StructuredQuery.Order]):
6161 The order to apply to the query results.
6262
63- Callers can provide a full ordering, a partial ordering, or
64- no ordering at all. While Firestore will always respect the
65- provided order, the behavior for queries without a full
66- ordering is different per database edition:
67-
68- In Standard edition, Firestore guarantees a stable ordering
69- through the following rules:
63+ Firestore allows callers to provide a full ordering, a
64+ partial ordering, or no ordering at all. In all cases,
65+ Firestore guarantees a stable ordering through the following
66+ rules:
7067
7168 - The ``order_by`` is required to reference all fields used
7269 with an inequality filter.
@@ -87,14 +84,6 @@ class StructuredQuery(proto.Message):
8784 ``WHERE a > 1 ORDER BY a ASC, __name__ ASC``
8885 - ``WHERE __name__ > ... AND a > 1`` becomes
8986 ``WHERE __name__ > ... AND a > 1 ORDER BY a ASC, __name__ ASC``
90-
91- In Enterprise edition, Firestore does not guarantee a stable
92- ordering. Instead it will pick the most efficient ordering
93- based on the indexes available at the time of query
94- execution. This will result in a different ordering for
95- queries that are otherwise identical. To ensure a stable
96- ordering, always include a unique field in the ``order_by``
97- clause, such as ``__name__``.
9887 start_at (google.cloud.firestore_v1.types.Cursor):
9988 A potential prefix of a position in the result set to start
10089 the query at.
0 commit comments