Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mass updates #12

Closed
bleonard opened this issue Sep 4, 2015 · 10 comments
Closed

mass updates #12

bleonard opened this issue Sep 4, 2015 · 10 comments

Comments

@bleonard
Copy link

bleonard commented Sep 4, 2015

is there a way to UPDATE table_name SET prop1=14 WHERE prop2='key' ?

@astigsen
Copy link
Contributor

astigsen commented Sep 4, 2015

In the Swift API you can do it like this:

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

@bleonard
Copy link
Author

bleonard commented Sep 4, 2015

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
Copy link
Author

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
Copy link
Contributor

alazier commented Oct 12, 2015

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
Copy link
Contributor

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

@alazier
Copy link
Contributor

alazier commented Oct 12, 2015

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
Copy link
Author

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
Copy link
Contributor

alazier commented Oct 13, 2015

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

@bleonard
Copy link
Author

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

alazier added a commit that referenced this issue Nov 14, 2015
7701ba1 Merge pull request #16 from realm/tg-close
883ef12 Add Realm::close() and call it in RealmCache::clear()
e9ca54e Merge pull request #12 from realm/tg-core-0.94.4
0823a62 Merge pull request #13 from realm/tg-is-empty
62f59d9 Merge pull request #15 from realm/tg-file-error-path
b93e5ce Include the path of the file which actually failed to open in exceptions
e1e9cd8 Add ObjectStore::is_empty()
52e7e61 Update for core 0.94.4
271432b Merge pull request #11 from realm/kd-rename-delegate-to-bindingcontext
db36ca5 Remove Realm suffix
70e1967 Rename realm delegate in transact_log_handler as well
4973827 Rename RealmDelegate to RealmBindingContext
347145b Merge pull request #8 from realm/mar-migrate-required-to-optional
0b45772 Add a test showing our behavior when migrating from an optional column to a required column.
9f1702a Support migrating required columns to optional, preserving their contents.
f5b790c Merge pull request #6 from realm/tg-impl
6dfeaf8 Move things which are not part of the API to an impl directory/namespace
513e483 Merge pull request #4 from realm/tg-realm
f646777 Send changes_available() even if autorefresh is enabled
21d32bf Add a bit of documentation for RealmDelegate
95c80c9 Fix error in cleanup after an error during a migration
b7936bb Simplify column shifting for removed properties a little
a0f1dab Add a Schema class, move lookup by name and internal-consistency checks there
b381437 Make Realm::compact() more robust
6133eeb Reduce the scope of a variable
0c111a2 Fix a comment
ba278c5 Fix checks for what types of columns can be optional
7de20ea USe more const refs to avoid copies
dbac77f Make a bunch of things const
1400450 Remove an unused function
06e0ff8 Share ExternalCommitHelpers between Realm instances for a single path
f79dec9 Allow more nullable property types when supported
0eb0bd1 Honor is_nullable when creating columns
ea5c475 Refactor schema initialization a bit
e4f29fe Move the interprocess notification functionality to the object store
b129ebe Shuffle stuff around and clean some things up
eeb2ddd Improve array KVO performance a bit
c3649fb Skip PK uniqueness checking when first creating a Realm file
0a41c85 Improve performance of realm_requires_update() and make more things const
efdfa08 Port some of the KVO support functionality to the object store
65e1eb5 Add the ability to bypass the Realm cache entirely
3f226cf Rework change notifications
045c7b2 Add Realm::get_schema_version()
e4377bb Change realm::Schema to a vector rather than a map
cae4cf2 Remove property.hpp include from object_schema.hpp
55e6cca Convert RLMRealmConfiguration to a wrapper around Realm::Config
563a837 Use NSDMIs for realm::Property
0ae1bb1 Don't cache dynamic realms in the ObjectStore cache either
25a6734 Eliminate some copies
45890f2 Use NSDMIs for Realm
348f4a7 Reduce s_init_mutex's scope
b4f856b Use NSDMIs for Realm::Config and make it moveable
a91839b Store a copy of the encryption key
0700428 Merge pull request #3 from realm/al-bugfixes
b084335 clear Realm cache between tests
cb8364c property copy schema from cached realms
8712c8b fixes for latest object store changes
453e4d8 Fix crash when adding a property to a model without updating the schema version.

git-subtree-dir: src/object-store
git-subtree-split: 7701ba1
tgoyne added a commit that referenced this issue Jan 4, 2016
@kneth
Copy link
Member

kneth commented Dec 5, 2017

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants