Add RealmList.removeAllFromRealm and Realm.clear

[beeender]

• Add LinkView.removeAllTargetRows.
• Add Realm.removeAll.
• Add Realm.remove(RealmObject).
• Add Realm.remove(Iterable).
• Javadoc & test case update.

Close #1560

[beeender]

@realm/java

[dalinaum]

How about rearranging items.

  * Added RealmQuery.isNotEmpty() (#2025). (Thank you @stk1m1)
  * Added Realm.remove(RealmObject), Realm.remove(Iterable) and Realm.removeAll() (#1560).
  * Improved performance of RealmList#contains() (#897).

[nhachicha]

what happens when a pending insert transaction is running in the background. I guess removeAll doesn't guarantee everything will be erased ( that's the user responsibility to cancel async transac & make sure the call return before calling removeAll

[beeender]

@nhachicha Yep, i think so. removeAll still needs to be called in the transaction and it will be user's responsibility to ensure the sequence of inserting and clearing.

[kneth]

Why not use the constants CLASS_CAT and CLASS_DOG?

[cmelchior]

@beeender Just noticed we have a Realm.clear(class). Should we rename clear() to clearAll() instead or is clear() and clear(class) good enough?

[beeender]

@cmelchior I don't have strong opinion on both names. We might be able to have another function which is close to the word clear is clear everything, objects and schemas. Maybe that fits clearAll better? Currently it is easy for user to figure out the clear() is just clear all objects because of clear(String classname) is there. Right? Any other good reason that we shall use clearAll here?

[cmelchior]

clear() fits the List API better, while clearAll() is a perhaps a bit easier to read if you don't know the method exists on the List interface. I think I'm fine with clear(), I just noticed it when doing something else.

[beeender]

retest this please and god bless me

[zaki50]

What does this test?

• IllegalStateException will be thrown if the RealmList is not managed.
• IllegalStateException will be thrown if the RealmList contains standalone object.

I think we should split this into two tests.

[zaki50]

oh, testRealmRemoveAllNotManagedList already exists and it does not throw the IllegalStateException.

so, this tests IllegalStateException will be thrown if the RealmList contains standalone object.

[beeender]

• "IllegalStateException will be thrown if the RealmList is not managed." This doesn't throw if every object is managed.
  See testRealmRemoveAllNotManagedList
• "IllegalStateException will be thrown if the RealmList contains standalone object." This is what this test do.
• A standalone object in a managed RealmList is not possible, so no test case for it.