Question

I’m working with ordered data and ran into this problem:

I add items to a location with push() and set their priority to their creation date in milliseconds so they are ordered by date. When I try to change the order of the items I find the next, or previous (if there’s no next) item and get it’s priority, then I add or substract one and set the priority of the moved item to the result. I fetch the priority ok, but when I call setPriority() the item loses the priority. Exporting the item with the graphical debugger returns no priority for each item moved. Returns correct priority for unmoved items.

Some code:

/* id is the id of the div being moved
using jquery ui's sortable
div id's are formed like "item_" + firebaseref.name()
*/
name = id.substr(id.indexOf('_') + 1);
id2 = $('#' + id).next().attr('id');
if(id2){
    name2 = id2.substr(id2.indexOf('_') + 1);
    itemRef = rootRef.child('path/to/my/items/'+name2);
    itemRef.once('value', function (dataSnapshot){
        var pr = Number(dataSnapshot.getPriority()),
        myRef = rootRef.child('path/to/my/items/'+name);
        myRef.setPriority(pr - 1); // tried this or toString as below
    });
} else {
// try previous item
    id2 = $('#' + id).prev().attr('id');
    if(id2){
        name2 = id2.substr(id2.indexOf('_') + 1);
        itemRef = rootRef.child('path/to/my/items/'+name2);
        itemRef.once('value', function (dataSnapshot){
            var pr = Number(dataSnapshot.getPriority()) + 1,
            myRef = rootRef.child('path/to/my/items/'+name);
            myRef.setPriority(pr.toString());
        });
    }
}

I had a ‘child_moved’ listener but I’m not using it now. Any ideas?

Answer 1

This is a bug in Firebase. I’m not sure of the cause at this point but it appears that numbers larger than a certain size are not being properly saved. We’ll investigate and update this answer when complete.

Update: This bug has been resolved. Give it another try!