Repository navigation
Order diff between backend and client with order_by_key() #677
Description
Describe your environment
- Operating System version: macOS 12.4
- Firebase SDK version: 6.1.0
- Firebase Product: database
- Python version: 3.7.9
- Pip version: 21.3.1
Describe the problem
When using order_by_key(), the order of the returned OrderedDict is not the same as the database making pagination very difficult
Steps to reproduce:
- Create a collection with this json in "/test" for example :
{
"123": {"myValue": true},
"100001": {"myValue": true},
"100002": {"myValue": true},
"100003": {"myValue": true},
"100004": {"myValue": true},
"100005": {"myValue": true}
}
- Query it with :
db.reference("/test").order_by_key().limit_to_first(4).get()- Comparison :
Current :
OrderedDict([('100001', {'myValue': True}), ('100002', {'myValue': True}), ('100003', {'myValue': True}), ('123', {'myValue': True})])
Expected :
OrderedDict([('123', {'myValue': True}), ('100001', {'myValue': True}), ('100002', {'myValue': True}), ('100003', {'myValue': True})])
Comments
So according to this link, order should be the same as the collection but in the corresponding OrderedDict the order is not the same so if you want make a pagination strategy, it just loops as getting the last key of the OrderedDict returned and using it in start_at will return the same result over and over again.
Activity
tperraut commentedon Mar 2, 2023
We fixed this issue on a fork replacing this line :
firebase-admin-python/firebase_admin/db.py
Line 622 in 5c21b81
by
So the client sorter is not triggered when ordering by key and we will have the same order as the database given here instead of a pure lexicographic one
tperraut commentedon Sep 2, 2026
up
fix(rtdb): Preserve server-side key order in order_by_key() query res…
fix(rtdb): Sort order_by_key() results the way the backend does