What is the problem with my index

[AAAATTIEH]

I have the following code to retrieve all members with revive/state = true

db.indexes.create('partners/*/members', 'revive/state');
db.query('partners/*/members')
    .filter('revive/state', '==', false)
    .get()
    .then(snapshots => {
        for (let snapshot of snapshots) {
            let data = snapshot.val();
            console.log(data.revive);
        }

    })
    .catch(error => {
        console.error('Error querying for renew=true:', error);
    });

When i query the data i got

[{
    state: false, //This is not correct cause i want only state = true 
},
{
   state: true, //This is correct 
}]

[appy-one]

I'll take a look at it. Can you post sample JSON data to test with?
One note though: you should await the index creation, it is probably not used by the query now

[AAAATTIEH]

Yes sure this is a sample json

{
  "partners": {
    "1115563526569978240": {
      "invites": {
        "12Wk45g733": { "uses": 0, "max": 100 },
        "12ZzABN2kW": { "uses": 0, "max": 100 }
      },
      "members": {
        "213213213": {
          "partner_id": "213213213",
          "guild_id": "1115563526569978240",
          "invite_code": "12ZzABN2kW",
          "timestamp": 1703155460591,
          "renewed": 0,

          "uses": 0,
          "manager_id": "997156698795645318",
          "unique_members": [],
          "all_members": [],
          "level": 1,
          "message_id": "1187344803885744131",
          "arrivals": [],
          "created_at": 1703155460591,
          "revive": {
            "number": 0,
            "state": false,
            "notification": false,
            "timestamp": 1703587460591
          },
          "sotw": { "state": false, "timestamp": 1703155460591 },
          "featured": { "state": false, "timestamp": 1703155460591 },
          "server": {
            "id": "911562263659871417",
            "name": "abc"
          }
        },
        "997156698795645318": {
          "partner_id": "997156698795645318",
          "guild_id": "1115563526569978240",
          "invite_code": "12Wk45g733",
          "timestamp": 1702972286282,
          "renewed": 8,

          "uses": 0,
          "manager_id": "997165651163795318",
          "unique_members": [],
          "all_members": [],
          "level": 6,
          "message_id": "1186577220806914058",
          "arrivals": [],
          "created_at": 1702972286282,
          "revive": { "state": true, "number": 8, "timestamp": 1703404454167 },
          "featured": { "state": true, "timestamp": 1703577132759 },
          "sotw": { "state": false, "timestamp": 1702972286282 },
          "server": {
            "id": "911562263659871417",
            "name": "abc"
          }
        }
      }
    }
  }
}

Querying first works but when i try to update one state from false to true or vice versa in members/id/revive/state using acebase server web interface for testing purposes it actually causes this issue and querying does not work as expected.

and with respect to await i did it before but forgot to include it in the sample code

[AAAATTIEH]

it's been two weeks any answer? @appy-one

[appy-one]

@AAAATTIEH I wrote a unit test using your data, but it passes every time:

await db.ref('partners').set({
    '1115563526569978240': {
        'invites': {
            '12Wk45g733': { 'uses': 0, 'max': 100 },
            '12ZzABN2kW': { 'uses': 0, 'max': 100 },
        },
        'members': {
            '213213213': {
                'partner_id': '213213213',
                'guild_id': '1115563526569978240',
                'invite_code': '12ZzABN2kW',
                'timestamp': 1703155460591,
                'renewed': 0,

                'uses': 0,
                'manager_id': '997156698795645318',
                'unique_members': [],
                'all_members': [],
                'level': 1,
                'message_id': '1187344803885744131',
                'arrivals': [],
                'created_at': 1703155460591,
                'revive': {
                    'number': 0,
                    'state': false,
                    'notification': false,
                    'timestamp': 1703587460591,
                },
                'sotw': { 'state': false, 'timestamp': 1703155460591 },
                'featured': { 'state': false, 'timestamp': 1703155460591 },
                'server': {
                    'id': '911562263659871417',
                    'name': 'abc',
                },
            },
            '997156698795645318': {
                'partner_id': '997156698795645318',
                'guild_id': '1115563526569978240',
                'invite_code': '12Wk45g733',
                'timestamp': 1702972286282,
                'renewed': 8,

                'uses': 0,
                'manager_id': '997165651163795318',
                'unique_members': [],
                'all_members': [],
                'level': 6,
                'message_id': '1186577220806914058',
                'arrivals': [],
                'created_at': 1702972286282,
                'revive': { 'state': true, 'number': 8, 'timestamp': 1703404454167 },
                'featured': { 'state': true, 'timestamp': 1703577132759 },
                'sotw': { 'state': false, 'timestamp': 1702972286282 },
                'server': {
                    'id': '911562263659871417',
                    'name': 'abc',
                },
            },
        },
    },
});
await db.indexes.create('partners/*/members', 'revive/state');
const snapshots = await db.query('partners/*/members')
    .filter('revive/state', '==', false)
    .get();
for (const snapshot of snapshots) {
    // 1 snapshot
    const data = snapshot.val();
    expect(data.revive.state).toBeFalse(); // -> pass
}

[talesmousinho]

your indexes files might be corrupted.
it happens with me when i force finish the process so the index file doesn't get updated.
when i delete the index's file and recreate the index it works well.

idk if it's your case but it worked for me.

[talesmousinho]

and i notice that at runtime you have to make sure that you create the index in the same AceBase instance you are using in your queries or the index won't get updated (i'm using cluster with multiple instances reading from one Acebase file)