Help required: query property

[Buggaboo]

Remaining issues (2020 May 25)

1. For example,.find(replaceNullWith:-2) on tLong works, but still not on the other integerish types.
2. Doubles could be initialized to null (expected), but floats are set to 0.0f by default, thus making replaceWithNull unnecessary. Same thing as last year.
3. Same syntax issue, we haven't addressed that at all. My gut feeling says we should apply extensions, and drop the generics.

So... I'm still stuck 6 months later. Ideas?

Remaining issues (2019 Nov 29)

1. Signed negative values are returned as unsigned values by the find function on tShort and tInteger properties, e.g. find(replaceNullWith: -2)
2. Float properties are never null, so regardless of the replaceNullWith parameter, uninitialized values will always return 0.0.
3. Casting to PropertyQuery is an unnecessary pain.

Right now we have:

final query = box.query(tInteger.greaterThan(0)).build();
final qp = query.property(tInteger);

Where tInteger is referenced to return the concrete IntegerPropertyQuery, but the return type is still the limiting factor, i.e. the compiler will make it PropertyQuery again, because the generic param <PQ extends PropertyQuery> requirement applies.

We could change the syntax:

final q = box.query(tInteger.greaterThan(0)).build();
final qp = (tInteger.query(q)..distinct = true).average(); // Entity_.tInteger.query function is generated
q.close(); qp.close();

[vaind]

I think I've found the bug you were looking for WRT count() - should be fine after applying the proposed change (name of the function).

I'll still have to think about how to accomplish having a properly typed find() method directly on query().build().property() without having to cast.

[greenrobot-team]

@Buggaboo I'm trying to finish this in #108, feedback is still welcome.

[greenrobot-team]

Merged as part of #108.