Wrong result when using x == NONE {y} about realm-java HOT 4 CLOSED

@jd565 Thank you for taking the time to report.

@ironage Do you have any ideas?

from realm-java.

Hi @jd565
Assuming 3 objects with member_ids of 100, 101, 102 then we'd expect the following matches for these queries:

We can read member_id == NONE {100, 101, 102} as "match all members who have a member_id that equals none of {100, 101, 102}".
From your expectations, I think you are looking to use the ANY query instead of NONE. Let me know if that works for you.

from realm-java.

@ironage Thanks for taking a look.
The table above is not the behaviour I am seeing.
I am inserting 100, 101 and 102 ids into the table, then have this code in a test:

        val nonMatching = realm.where<RealmProfile>()
            .rawPredicate("${RealmProfile.MEMBER_ID} == NONE {100}")
            .findAll()
            .map { it.memberID }
        assertEquals(listOf(101, 102), nonMatching)

that is, I want to find all the profiles without member id 100, expecting this to return just the members with id 101 and 102, but my test fails with the following:

java.lang.AssertionError: expected:<[101, 102]> but was:<[100]>

Suggesting that the raw predicate is not doing what you have outlined in your message above.

If I have multiple items inside the NONE, like NONE {100, 101}, then the query correctly returns only member 102, so it seems to only be a problem when a single element is inside the NONE query

from realm-java.

@jd565 thanks for the clarification. I wasn't able to reproduce, until I add an index to test property (this applies to you if member_id is a primary key or if you have added an index manually). I submitted a fix in realm/realm-core#7333, but until that lands, I'd suggest that you change your query to be member_id != ALL {...} which should produce equivalent results for the time being. Thanks for reporting this bug to us!

from realm-java.