I have inserted data like this into Firebase Real-Time Database like this way:
And I query the database back like this way:
final database
As soon as you call firstPageItems = snapshot.value
, you are converting the results into a map/dictionary. A dictionary can hold the keys and the values of the results, but it has no place for the relative order of the results.
To maintain the order of the results, you'll want to either observe onChildAdded
:
var query = databaseReference
.child('orders')
.orderByChild('date_slug')
.limitToFirst(pageSize);
query.onChildAdded
.forEach((event) => {
print(event.snapshot.value)
});
If you need to know when all child nodes of your query have been handled, you can add an additional listener to the value event:
query.once().then((snapshot) {
print("Done loading all data for query");
});
Adding this additional listener does not result in downloading extra data, as Firebase deduplicates then behind the scenes.
Alternatively, you can the FirebaseList class from the FlutterFire library, which uses that same onChildAdded
and the other onChild...
streams to maintain an indexed list.
An example of using this class:
list = FirebaseList(query: query,
onChildAdded: (pos, snapshot) {},
onChildRemoved: (pos, snapshot) {},
onChildChanged: (pos, snapshot) {},
onChildMoved: (oldpos, newpos, snapshot) {},
onValue: (snapshot) {
for (var i=0; i < this.list.length; i++) {
print('$i: ${list[i].value}');
}
}
);
As you can see this uses the onValue
stream of the list to loop over the children in order. The onChild...
methods are needed for the FirebaseList
class, but we don't do anything meaningful with them here.