On this page
- Method Summary
- Inherited Methods
- Constructor Detail
- Method Detail
RealmConfiguration.Builder used to construct instances of a RealmConfiguration in a fluent manner.
Constructor and Description
Creates an instance of the Builder for the RealmConfiguration.
Modifier and Type
Method and Description
public final RealmConfiguration.Builder
Creates the RealmConfiguration based on the builder parameters.
Setting this will cause Realm to compact the Realm file if the Realm file has grown too large and a significant amount of space can be recovered.
Setting this will change the behavior of how migration exceptions are handled.
Sets the 64 byte key used to encrypt and decrypt the Realm file.
Setting this will create an in-memory Realm instead of saving it to disk.
Sets the schema version of the Realm.
Methods inherited from class java.lang.Object :
Creates an instance of the Builder for the RealmConfiguration.This will use the app's own internal directory for storing the Realm file. This does not require any additional permissions. The default location is
Sets whether or not a RealmQuery can be launched from the UI thread.
By default Realm allows queries on the main thread. However, by doing so your application may experience a drop of frames or even ANRs. We recommend diverting queries to non-UI threads or, alternatively, using RealmQuery.findAllAsync() or RealmQuery.findFirstAsync() .
Sets whether or not calls to Realm.executeTransaction are allowed from the UI thread.
WARNING: Realm does not allow synchronous transactions to be run on the main thread unless users explicitly opt in with this method. We recommend diverting calls to
Copies the Realm file from the given asset file path.When opening the Realm for the first time, instead of creating an empty file, the Realm file will be copied from the provided asset file and used instead.
This cannot be combined with deleteRealmIfMigrationNeeded() as doing so would just result in the copied file being deleted.
WARNING: This could potentially be a lengthy operation and should ideally be done on a background thread.
Sets this to determine if the Realm file should be compacted before returned to the user. It is passed the total file size (data + free space) and the bytes used by data in the file.
Setting this will change the behavior of how migration exceptions are handled. Instead of throwing a io.realm.exceptions.RealmMigrationNeededException the on-disc Realm will be cleared and recreated with the new Realm schema.
This cannot be configured to have an asset file at the same time by calling assetFile(String) as the provided asset file will be deleted in migrations.
WARNING! This will result in loss of data.
Specifies the directory where the Realm file will be saved. The default value is
Setting this will create an in-memory Realm instead of saving it to disk. In-memory Realms might still use disk space if memory is running low, but all files created by an in-memory Realm will be deleted when the Realm is closed.Note that because in-memory Realms are not persisted, you must be sure to hold on to at least one non-closed reference to the in-memory Realm object with the specific name as long as you want the data to last.
Sets the maximum number of live versions in the Realm file before an IllegalStateException is thrown when attempting to write more data.
Realm is capable of concurrently handling many different versions of Realm objects. This can e.g. happen if you have a Realm open on many different threads or are freezing objects while data is being written to the file.
Under normal circumstances this is not a problem, but if the number of active versions grow too large, it will have a negative effect on the filesize on disk. Setting this parameters can therefore be used to prevent uses of Realm that can result in very large Realms.
Replaces the existing module(s) with one or more RealmModule s. Using this method will replace the current schema for this Realm with the schema defined by the provided modules.
A reference to the default Realm module containing all Realm classes in the project (but not dependencies), can be found using Realm.getDefaultModule() . Combining the schema from the app project and a library dependency is thus done using the following code:
Setting this will cause the Realm to become read only and all write transactions made against this Realm will fail with an IllegalStateException .
Marking a Realm as read only only applies to the Realm in this process. Other processes can still write to the Realm.
Sets the schema version of the Realm. This must be equal to or higher than the schema version of the existing Realm file, if any. If the schema version is higher than the already existing Realm, a migration is needed.If no migration code is provided, Realm will throw a io.realm.exceptions.RealmMigrationNeededException .