mass updates about realm-js

[astigsen]

In the Swift API you can do it like this:

realm.objects(MyClass).filter("prop2='key'").setValue(14, forKey: "prop1")

[bleonard]

you guys are so fancy with your chaining!
I don't have the immediate need, but would do something like that in JS eventually.

[bleonard]

It feels pretty inefficient to be looping in javascript to set a bunch of rows. Our MySQL equivalent use case is UPDATE jobs SET state='inactive' WHERE id NOT IN(array)

[alazier]

In the short term we plan to support more js array methods including foreach and map. This should allow you to update each item without having to explicitly loop through each item, although underneath the hood we will still have a loop at some level.

[astigsen]

Is there any reason that we can't just implement the setValue() method in js as well?

[alazier]

We could but this concept may be foreign to most js developers. We implemented setValue() in swift as setting values by keyPath is built into cocoa and expected by cocoa developers. My understanding is that the analogous functionality in JS is forEach and map. Adding setValue() would should be lower priority that these expected methods and wouldn't gain much as we would still have to loop through all elements (although we could avoid creating JS accessors).

[bleonard]

But it's not foreign to people that have been using sqlite/coredata in iOS that are now switching to React / Realm. Most engineers would assume it's significantly slower to do the iteration. That could be a big deal depending on the scale and they might be willing to deviate from common JS practices.

[alazier]

Fair point. This is a feature that power users may expect and becomes much more important with larger data sets.

[bleonard]

to be clear, our set is not big enough for this to be a blocker, but just trying to help your success.

[kneth]

Realm JS 2.0.0 introduced Realm.Results.update().