Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It doesn't make sense to iterate through all address books to call insert methods for contacts and address items as when you call
realm.insertOrUpdate(finalAddressBooks)
, all contacts and addresses referenced are also inserted. This is similar to DBFlowTester calling onlySaver.saveAll(finalAddressBooks)
, without needing to call this same method for contacts and address items.Call
insertOrUpdate()
instead ofcopyToRealm()
, as we are concerned only about inserting these entities, and not retrieving the newly inserted items.insertOrUpdate()
doesn't return the inserted entites, and as stated in the docs, this makes it run faster.Update Realm version.