Local Data Store Object Repository
Functions
Removes the object in scope in a synchronous way. It removes the value in the database and propagates the changes to modify the DataObject.syncState of the parent, so it's updated in the server in the next upload. It blocks the thread and finishes as soon as the object is deleted in the database.
Removes the object in scope in a synchronous way. It removes the value in the database and propagates the changes to modify the DataObject.syncState of the parent, so it's updated in the server in the next upload. 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. It removes the value in the database and propagates the changes to modify the DataObject.syncState of the parent, so it's updated in the server in the next upload. 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 an asynchronous way. It removes the value in the database and propagates the changes to modify the DataObject.syncState of the parent, so it's updated in the server in the next upload. It returns a Completable
that completes as soon as the object is deleted in the database. 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.
Returns the object in an asynchronous way, returning a Single<M>
.