Array of Primitives: Support queries #5361
Comments
I actually think
has a higher importance than the others, so that you can replace |
Yes. No doubt about that |
Any progress/updates on this? I am eagerly waiting for this feature to support the primitive list from my Wordpress API the native way without a wrapper. :) |
Agreed, I was hoping for end of 2017, but maybe this year Surprised it's blocked, I thought subtable query does this. |
+1, I have to use |
@mgohin another option of course is to map the list into a single string field with some convention like But that's lame that we still have to do that, i agree |
+1 |
Hi, |
Hi @Zhuinden Any updates for this or what is the best workaround that u suggest for this |
It's something we expect to prioritize "soonish" - but we are currently prioritizing getting Core6 tested, integrated and rolled out. I know that doesn't say much in terms of timeline, but it's unlikely to happen on this side of New Year. |
@bmunkholm |
@ismdcf I've already posted the workaround, as unfortunate as it is: #5361 (comment) For Realm's roadmap, take a look at https://www.mongodb.com/realm#roadmap
So you should probably map them to a single String field with separators and expect the feature for July 2020. The good old |
This has now been implemented in Core and ObjectStore, awaiting implementation here. |
➤ Claus Rørbech commented: The currently used old syntax for queries does not support querying on primitive list elements. Filed this with core in RCORE-309. |
Split from #5031
We need to add support for arrays of values to
RealmQuery
. Based on API discussions we don't want to add a ton of extra methods, so instead we are going to use the empty field name""
when querying arrays of primitives.E.g
This also include support for
RealmList.min()/max()/average()/sum()/minDate()/maxDate()
which depends on the query systemOut of scope for now
The text was updated successfully, but these errors were encountered: