LocalDataStoreObjectRepository

Functions

Link copied to clipboard
open override fun blockingDelete()

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.

Link copied to clipboard
open override fun blockingDeleteIfExist()

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.

Link copied to clipboard
open override fun blockingExists(): Boolean

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.

Link copied to clipboard
open override fun blockingGet(): KeyValuePair?

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.

Link copied to clipboard
Link copied to clipboard
open override fun blockingSet(value: String?)
Link copied to clipboard
open override fun delete(): Completable

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.

Link copied to clipboard
open override fun deleteIfExist(): Completable

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.

Link copied to clipboard
open override fun exists(): Single<Boolean>

Returns if the object exists in an asynchronous way, returning a Single<Boolean>.

Link copied to clipboard
open override fun get(): Single<KeyValuePair?>

Returns the object in an asynchronous way, returning a Single<M>.

Link copied to clipboard
open override fun set(value: String?): Completable

Sets the object in scope in an asynchronous way. It returns a Completable which is completed when the object is updated to the database. It adds an object with a ASDASDASDASDASD which will be uploaded to the server in the next upload.