-
Notifications
You must be signed in to change notification settings - Fork 624
Key comparison for RTDB queries should correctly handle boundary sentinels #2328
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Coverage ReportAffected SDKs
Test Logs
NotesHTML coverage reports can be produced locally with Head commit (aedfc809) is created by Prow via merging commits: 998b18a 6f741f3. |
Binary Size ReportAffected SDKs
Test Logs
NotesHead commit (aedfc809) is created by Prow via merging commits: 998b18a 6f741f3. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm. Should we update the comparison function instead? This bug can show up in a number of places.
@IanWyszynski: The following tests failed, say
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
In order for
startAfter
andendBefore
to have the correct ordering semantics, we need to return the objectsMAX_KEY
andMIN_KEY
. Otherwise, the comparison function won't work properly in all cases:https://github.com/firebase/firebase-android-sdk/blob/master/firebase-database/src/main/java/com/google/firebase/database/snapshot/ChildKey.java#L74-L76