RLMRealmConfiguration
@interface RLMRealmConfiguration : NSObject <NSCopying>
An RLMRealmConfiguration
instance describes the different options used to
create an instance of a Realm.
RLMRealmConfiguration
instances are just plain NSObject
s. Unlike RLMRealm
s
and RLMObject
s, they can be freely shared between threads as long as you do not
mutate them.
Creating configuration objects for class subsets (by setting the
objectClasses
property) can be expensive. Because of this, you will normally want to
cache and reuse a single configuration object for each distinct configuration rather than
creating a new object each time you open a Realm.
-
Returns the default configuration used to create Realms when no other configuration is explicitly specified (i.e.
+[RLMRealm defaultRealm]
).Declaration
Objective-C
+ (nonnull instancetype)defaultConfiguration;
Return Value
The default Realm configuration.
-
Sets the default configuration to the given
RLMRealmConfiguration
.Declaration
Objective-C
+ (void)setDefaultConfiguration:(nonnull RLMRealmConfiguration *)configuration;
Parameters
configuration
The new default Realm configuration.
-
The local URL of the Realm file. Mutually exclusive with
inMemoryIdentifier
; setting one of the two properties will automatically nil out the other.Declaration
Objective-C
@property (readwrite, copy, nonatomic, nullable) NSURL *fileURL;
-
A string used to identify a particular in-memory Realm. Mutually exclusive with
fileURL
andsyncConfiguration
; setting any one of the three properties will automatically nil out the other two.Declaration
Objective-C
@property (readwrite, copy, nonatomic, nullable) NSString *inMemoryIdentifier;
-
A 64-byte key to use to encrypt the data, or
nil
if encryption is not enabled.Declaration
Objective-C
@property (readwrite, copy, nonatomic, nullable) NSData *encryptionKey;
-
Whether to open the Realm in read-only mode.
This is required to be able to open Realm files which are not writeable or are in a directory which is not writeable. This should only be used on files which will not be modified by anyone while they are open, and not just to get a read-only view of a file which may be written to by another thread or process. Opening in read-only mode requires disabling Realm’s reader/writer coordination, so committing a write transaction from another process will result in crashes.
Declaration
Objective-C
@property (assign, readwrite, nonatomic) BOOL readOnly;
-
The current schema version.
Declaration
Objective-C
@property (assign, readwrite, nonatomic) uint64_t schemaVersion;
-
The block which migrates the Realm to the current version.
Declaration
Objective-C
@property (readwrite, copy, nonatomic, nullable) RLMMigrationBlock migrationBlock;
-
Whether to recreate the Realm file with the provided schema if a migration is required. This is the case when the stored schema differs from the provided schema or the stored schema version differs from the version on this configuration. Setting this property to
YES
deletes the file if a migration would otherwise be required or executed.Note
Setting this property toYES
doesn’t disable file format migrations.Declaration
Objective-C
@property (assign, readwrite, nonatomic) BOOL deleteRealmIfMigrationNeeded;
-
A block called when opening a Realm for the first time during the life of a process to determine if it should be compacted before being returned to the user. It is passed the total file size (data + free space) and the total bytes used by data in the file.
Return
YES
to indicate that an attempt to compact the file should be made. The compaction will be skipped if another process is accessing it.Declaration
Objective-C
@property (readwrite, copy, nonatomic, nullable) RLMShouldCompactOnLaunchBlock shouldCompactOnLaunch;
-
The classes managed by the Realm.
Declaration
Objective-C
@property (readwrite, copy, nonatomic, nullable) NSArray *objectClasses;
-
The maximum number of live versions in the Realm file before an exception will be thrown when attempting to start a write transaction.
Realm provides MVCC snapshot isolation, meaning that writes on one thread do not overwrite data being read on another thread, and instead write a new copy of that data. When a Realm refreshes it updates to the latest version of the data and releases the old versions, allowing them to be overwritten by subsequent write transactions.
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. This can happen when performing writes on many different threads at once, when holding on to frozen objects for an extended time, or when performing long operations on background threads which do not allow the Realm to refresh.
Setting this property to a non-zero value makes it so that exceeding the set number of versions will instead throw an exception. This can be used with a low value during development to help identify places that may be problematic, or in production use to cause the app to crash rather than produce a Realm file which is too large to be oened.
Declaration
Objective-C
@property (assign, readwrite, nonatomic) NSUInteger maximumNumberOfActiveVersions;
-
A configuration object representing configuration state for Realms intended to sync with a Realm Object Server.
This property is mutually exclusive with both
inMemoryIdentifier
andfileURL
; setting any one of the three properties will automatically nil out the other two.Declaration
Objective-C
@property (assign, readwrite, nonatomic, nullable) RLMSyncConfiguration *syncConfiguration;
Swift
var syncConfiguration: RLMSyncConfiguration? { get set }