Event Object Repository
Functions
Removes the object in scope in a synchronous way. Field DataObject.syncState is marked as State.TO_UPDATE and DeletableDataObject.deleted as true. In the next upload, it will be deleted in the server. It blocks the thread and finishes as soon as the object is deleted in the database. It throws an exception if the object doesn't exist.
Removes the object in scope in an asynchronous way. Field DataObject.syncState is marked as State.TO_POST and DeletableDataObject.deleted as true. Unlike .blockingDelete, it doesn't throw an exception if the object doesn't exist. It blocks the thread and finishes as soon as the object is deleted in the database.
Returns if the object exists in a synchronous way. Important: this is a blocking method and it should not be executed in the main thread. Consider the asynchronous version .exists.
Returns the object in a synchronous way. Important: this is a blocking method and it should not be executed in the main thread. Consider the asynchronous version .get.
Removes the object in scope in an asynchronous way. Field DataObject.syncState is marked as State.TO_UPDATE and DeletableDataObject.deleted as true. In the next upload, it will be deleted in the server. It returns a Completable
that completes as soon as the object is deleted in the database. The Completable
fails if the object doesn't exist.
Removes the object in scope in a synchronous way. Field DataObject.syncState is marked as State.TO_POST and DeletableDataObject.deleted as true. Unlike .delete, it doesn't throw an exception if the object doesn't exist. It returns a Completable
that completes as soon as the object is deleted in the database.