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
{{ message }}
This repository was archived by the owner on Apr 28, 2026. It is now read-only.
This issue is for tracking the various query "edge-cases" that are probably worth documenting
The following is a non-exhaustive list of points to cover:
.orderBy().startAt().orderBy()
The issue: orderBy cannot be used if startAt was already specified
collection.startAt()
The issue: startAt requires an orderBy query
where('foo', >=).where('bar', >=)
The issue: when using certain where operators, subsequent where usages must be applied to the same property
This other list contains ODM-specific points:
This issue is for tracking the various query "edge-cases" that are probably worth documenting
The following is a non-exhaustive list of points to cover:
.orderBy().startAt().orderBy()
The issue: orderBy cannot be used if startAt was already specified
collection.startAt()
The issue: startAt requires an orderBy query
where('foo', >=).where('bar', >=)
The issue: when using certain where operators, subsequent where usages must be applied to the same property
This other list contains ODM-specific points:
orderByA().orderByB(startAt: )
copied from: firebase/flutterfire#9165