- Deprecate
migrateRealm:
in favor of newperformMigrationForConfiguration:error:
method that follows Cocoa's' NSError conventions. - Fix issue where
RLMResults
usedid
instead of its generic type type as the return type of subscript. - Fix incorrect truncation of the constant value for queries of the form
column < value
forfloat
anddouble
columns.
- Improve error message when using NSNumber incorrectly in Swift models.
- Fix compilation with Swift 2.3 using Xcode 8 beta 2.
- Further reduce the download size of the prebuilt static libraries.
- Improve sort performance, especially on non-nullable columns.
- Allow partial initialization of object by
initWithValue:
, deferring required property checks until object is added to Realm.
- Fix crash when an aggregate is accessed as an
Int8
,Int16
,Int32
, orInt64
. - Fix a race condition that could lead to a crash if an RLMArray or List was deallocated on a different thread than it was created on.
- Fix a crash when the last reference to an observed object is released from within the observation.
- Fix a crash when
initWithValue:
is used to create a nested object for a class with an uninitialized schema. - Enforce uniqueness for
RealmOptional
primary keys when using thevalue
setter.
- Attempting to add an object with no properties to a Realm now throws rather than silently doing nothing.
- Swift: A
write
block may nowthrow
, reverting any changes already made in the transaction. - Reduce address space used when committing write transactions.
- Significantly reduce the download size of prebuilt binaries and slightly reduce the final size contribution of Realm to applications.
- Improve performance of accessing RLMArray properties and creating objects with List properties.
- Fix a crash when reading the shared schema from an observed Swift object.
- Fix crashes or incorrect results when passing an array of values to
createOrUpdate
after reordering the class's properties. - Ensure that the initial call of a Results notification block is always passed .Initial even if there is a write transaction between when the notification is added and when the first notification is delivered.
- Fix a crash when deleting all objects in a Realm while fast-enumerating query results from that Realm.
- Handle EINTR from flock() rather than crashing.
- Fix incorrect behavior following a call to
[RLMRealm compact]
. - Fix live updating and notifications for Results created from a predicate involving an inverse relationship to be triggered when an object at the other end of the relationship is modified.
- None.
- Significantly improve performance of opening Realm files, and slightly improve performance of committing write transactions.
- Swift: Fix an error thrown when trying to create or update
Object
instances viaadd(:_update:)
with a primary key property of typeRealmOptional
. - Xcode playground in Swift release zip now runs successfully.
- The
key
parameter ofRealm.objectForPrimaryKey(_:key:)
/Realm.dynamicObjectForPrimaryKey(_:key:)
is now marked as optional. - Fix a potential memory leak when closing Realms after a Realm file has been opened on multiple threads which are running in active run loops.
- Fix notifications breaking on tvOS after a very large number of write transactions have been committed.
- Fix a "Destruction of mutex in use" assertion failure after an error while opening a file.
- Realm now throws an exception if an
Object
subclass is defined with a managed Swiftlazy
property. Objects with ignoredlazy
properties should now work correctly. - Update the LLDB script to work with recent changes to the implementation of
RLMResults
. - Fix an assertion failure when a Realm file is deleted while it is still open, and then a new Realm is opened at the same path. Note that this is still not a supported scenario, and may break in other ways.
No changes since 0.103.2.
- None.
- Improve the error messages when an I/O error occurs in
writeCopyToURL
.
- Fix an assertion failure which could occur when opening a Realm after opening that Realm failed previously in some specific ways in the same run of the application.
- Reading optional integers, floats, and doubles from within a migration block
now correctly returns
nil
rather than 0 when the stored value isnil
.
- None.
- None.
- Fix a bug that sometimes resulted in a single object's NSData properties
changing from
nil
to a zero-length non-nil
NSData when a different object of the same type was deleted.
- All functionality deprecated in previous releases has been removed entirely.
- Support for Xcode 6.x & Swift prior to 2.2 has been completely removed.
RLMResults
/Results
now become empty when aRLMArray
/List
or object they depend on is deleted, rather than throwing an exception when accessed.- Migrations are no longer run when
deleteRealmIfMigrationNeeded
is set, recreating the file instead.
- Added
invalidated
properties toRLMResults
/Results
,RLMLinkingObjects
/LinkingObjects
,RealmCollectionType
andAnyRealmCollection
. These properties report whether the Realm the object is associated with has been invalidated. - Some
NSError
s created by Realm now have more descriptive user info payloads.
- None.
- None.
- Return
RLMErrorSchemaMismatch
error rather than the more genericRLMErrorFail
when a migration is required. - Improve the performance of allocating instances of
Object
subclasses that haveLinkingObjects
properties.
RLMLinkingObjects
properties declared in Swift subclasses ofRLMObject
now work correctly.- Fix an assertion failure when deleting all objects of a type, inserting more objects, and then deleting some of the newly inserted objects within a single write transaction when there is an active notification block for a different object type which links to the objects being deleted.
- Fix crashes and/or incorrect results when querying over multiple levels of
LinkingObjects
properties. - Fix opening read-only Realms on multiple threads at once.
- Fix a
BadTransactLog
exception when storing dates before the unix epoch (1970-01-01).
- None.
- Add a method to rename properties during migrations:
- Swift:
Migration.renamePropertyForClass(_:oldName:newName:)
- Objective-C:
-[RLMMigration renamePropertyForClass:oldName:newName:]
- Swift:
- Add
deleteRealmIfMigrationNeeded
toRLMRealmConfiguration
/Realm.Configuration
. When this is set totrue
, the Realm file will be automatically deleted and recreated when there is a schema mismatch rather than migrated to the new schema.
- Fix
BETWEEN
queries that traverseRLMArray
/List
properties to ensure that a single related object satisfies theBETWEEN
criteria, rather than allowing different objects in the array to satisfy the lower and upper bounds. - Fix a race condition when a Realm is opened on one thread while it is in the middle of being closed on another thread which could result in crashes.
- Fix a bug which could result in changes made on one thread being applied incorrectly on other threads when those threads are refreshed.
- Fix crash when migrating to the new date format introduced in 0.101.0.
- Fix crash when querying inverse relationships when objects are deleted.
- Files written by this version of Realm cannot be read by older versions of Realm. Existing files will automatically be upgraded when they are opened.
- Greatly improve performance of collection change calculation for complex object graphs, especially for ones with cycles.
- NSDate properties now support nanoseconds precision.
- Opening a single Realm file on multiple threads now shares a single memory mapping of the file for all threads, significantly reducing the memory required to work with large files.
- Crashing while in the middle of a write transaction no longer blocks other processes from performing write transactions on the same file.
- Improve the performance of refreshing a Realm (including via autorefresh) when there are live Results/RLMResults objects for that Realm.
- Fix an assertion failure of "!more_before || index >= std::prev(it)->second)"
in
IndexSet::do_add()
. - Fix a crash when an
RLMArray
orList
object is destroyed from the wrong thread.
-[RLMObject linkingObjectsOfClass:forProperty]
andObject.linkingObjects(_:forProperty:)
are deprecated in favor of properties of typeRLMLinkingObjects
/LinkingObjects
.
- The automatically-maintained inverse direction of relationships can now be exposed as
properties of type
RLMLinkingObjects
/LinkingObjects
. These properties automatically update to reflect the objects that link to the target object, can be used in queries, and can be filtered like other Realm collection types. - Queries that compare objects for equality now support multi-level key paths.
- Fix an assertion failure when a second write transaction is committed after a write transaction deleted the object containing an RLMArray/List which had an active notification block.
- Queries that compare
RLMArray
/List
properties using != now give the correct results.
- None.
- None.
- Fix a scenario that could lead to the assertion failure "m_advancer_sg->get_version_of_current_transaction() == new_notifiers.front()->version()".
- Deprecate properties of type
id
/AnyObject
. This type was rarely used, rarely useful and unsupported in every other Realm binding. - The block for
-[RLMArray addNotificationBlock:]
and-[RLMResults addNotificationBlock:]
now takes another parameter. - The following Objective-C APIs have been deprecated in favor of newer or preferred versions:
Deprecated API | New API |
---|---|
-[RLMRealm removeNotification:] |
-[RLMNotificationToken stop] |
RLMRealmConfiguration.path |
RLMRealmConfiguration.fileURL |
RLMRealm.path |
RLMRealmConfiguration.fileURL |
RLMRealm.readOnly |
RLMRealmConfiguration.readOnly |
+[RLMRealm realmWithPath:] |
+[RLMRealm realmWithURL:] |
+[RLMRealm writeCopyToPath:error:] |
+[RLMRealm writeCopyToURL:encryptionKey:error:] |
+[RLMRealm writeCopyToPath:encryptionKey:error:] |
+[RLMRealm writeCopyToURL:encryptionKey:error:] |
+[RLMRealm schemaVersionAtPath:error:] |
+[RLMRealm schemaVersionAtURL:encryptionKey:error:] |
+[RLMRealm schemaVersionAtPath:encryptionKey:error:] |
+[RLMRealm schemaVersionAtURL:encryptionKey:error:] |
- The following Swift APIs have been deprecated in favor of newer or preferred versions:
Deprecated API | New API |
---|---|
Realm.removeNotification(_:) |
NotificationToken.stop() |
Realm.Configuration.path |
Realm.Configuration.fileURL |
Realm.path |
Realm.Configuration.fileURL |
Realm.readOnly |
Realm.Configuration.readOnly |
Realm.writeCopyToPath(_:encryptionKey:) |
Realm.writeCopyToURL(_:encryptionKey:) |
schemaVersionAtPath(_:encryptionKey:error:) |
schemaVersionAtURL(_:encryptionKey:) |
- Add information about what rows were added, removed, or modified to the notifications sent to the Realm collections.
- Improve error when illegally appending to an
RLMArray
/List
property from a default value or the standalone initializer (init()
) before the schema is ready.
- Fix a use-after-free when an associated object's dealloc method is used to remove observers from an RLMObject.
- Fix a small memory leak each time a Realm file is opened.
- Return a recoverable
RLMErrorAddressSpaceExhausted
error rather than crash when there is insufficient available address space on Realm initialization or write commit.
- None.
- None.
- Fixed a bug that caused some encrypted files created using
-[RLMRealm writeCopyToPath:encryptionKey:error:]
to fail to open.
- None.
- None.
- Mark further initializers in Objective-C as NS_DESIGNATED_INITIALIZER to prevent that these aren't correctly defined in Swift Object subclasses, which don't qualify for auto-inheriting the required initializers.
-[RLMResults indexOfObjectWithPredicate:]
now returns correct results forRLMResults
instances that were created by filtering anRLMArray
.- Adjust how RLMObjects are destroyed in order to support using an associated object on an RLMObject to remove KVO observers from that RLMObject.
-[RLMResults indexOfObjectWithPredicate:]
now returns the index of the first matching object for a sortedRLMResults
, matching its documented behavior.- Fix a crash when canceling a transaction that set a relationship.
- Fix a crash when a query referenced a deleted object.
Prebuilt frameworks are now built with Xcode 7.3.
- None.
- None.
- Fix running unit tests on iOS simulators and devices with Xcode 7.3.
- None.
- None.
- Fix a crash when opening a Realm on 32-bit iOS devices.
- None.
- None.
- Properly report changes made by adding an object to a Realm with addOrUpdate:/createOrUpdate: to KVO observers for existing objects with that primary key.
- Fix crashes and assorted issues when a migration which added object link properties is rolled back due to an error in the migration block.
- Fix assertion failures when deleting objects within a migration block of a type which had an object link property added in that migration.
- Fix an assertion failure in
Query::apply_patch
when updating certain kinds of queries after a write transaction is committed.
- Initializing the shared schema is 3x faster.
- Using Realm Objective-C from Swift while having Realm Swift linked no longer causes that the
declared
ignoredProperties
are not taken into account. - Fix assertion failures when rolling back a migration which added Object link properties to a class.
- Fix potential errors when cancelling a write transaction which modified
multiple
RLMArray
/List
properties. - Report the correct value for inWriteTransaction after attempting to commit a write transaction fails.
- Support CocoaPods 1.0 beginning from prerelease 1.0.0.beta.4 while retaining backwards compatibility with 0.39.
- None.
- Aggregate operations (
ANY
,NONE
,@count
,SUBQUERY
, etc.) are now supported for key paths that begin with an object relationship so long as there is aRLMArray
/List
property at some point in a key path. - Predicates of the form
%@ IN arrayProperty
are now supported.
- Use of KVC collection operators on Swift collection types no longer throws an exception.
- Fix reporting of inWriteTransaction in notifications triggered by
beginWriteTransaction
. - The contents of
List
andOptional
properties are now correctly preserved when copying a Swift object from one Realm to another, and performing other operations that result in a Swift object graph being recursively traversed from Objective-C. - Fix a deadlock when queries are performed within a Realm notification block.
- The
ANY
/SOME
/NONE
qualifiers are now required in comparisons involving a key path that traverse aRLMArray
/List
property. Previously they were only required if the first key in the key path was anRLMArray
/List
property. - Fix several scenarios where the default schema would be initialized
incorrectly if the first Realm opened used a restricted class subset (via
objectClasses
/objectTypes
).
- Fix crashes when deleting an object containing an
RLMArray
/List
which had previously been queried. - Fix a crash when deleting an object containing an
RLMArray
/List
with active notification blocks. - Fix duplicate file warnings when building via CocoaPods.
- Fix crash or incorrect results when calling
indexOfObject:
on anRLMResults
derived from anRLMArray
.
+[RLMRealm realmWithPath:]
/Realm.init(path:)
now inherits from the default configuration.- Swift 1.2 is no longer supported.
- Add
addNotificationBlock
toRLMResults
,Results
,RLMArray
, andList
, which calls the given block whenever the collection changes. - Do a lot of the work for keeping
RLMResults
/Results
up-to-date after write transactions on a background thread to help avoid blocking the main thread. NSPredicate
'sSUBQUERY
operator is now supported. It has the following limitations:@count
is the only operator that may be applied to theSUBQUERY
expression.- The
SUBQUERY(…).@count
expression must be compared with a constant. - Correlated subqueries are not yet supported.
- None.
- None.
- Swift: Added
Error
enum allowing to catch errors e.g. thrown on initializingRLMRealm
/Realm
instances. - Fail with
RLMErrorFileNotFound
instead of the more genericRLMErrorFileAccess
, if no file was found when a realm was opened as read-only or if the directory part of the specified path was not found when a copy should be written. - Greatly improve performance when deleting objects with one or more indexed properties.
- Indexing
BOOL
/Bool
andNSDate
properties are now supported. - Swift: Add support for indexing optional properties.
- Fix incorrect results or crashes when using
-[RLMResults setValue:forKey:]
on an RLMResults which was filtered on the key being set. - Fix crashes when an RLMRealm is deallocated from the wrong thread.
- Fix incorrect results from aggregate methods on
Results
/RLMResults
after objects which were previously in the results are deleted. - Fix a crash when adding a new property to an existing class with over a million objects in the Realm.
- Fix errors when opening encrypted Realm files created with writeCopyToPath.
- Fix crashes or incorrect results for queries that use relationship equality
in cases where the
RLMResults
is kept alive and instances of the target class of the relationship are deleted.
- All functionality deprecated in previous releases has been removed entirely.
- Add generic type annotations to NSArrays and NSDictionaries in public APIs.
- Adding a Realm notification block on a thread not currently running from within a run loop throws an exception rather than silently never calling the notification block.
- Support for tvOS.
- Support for building Realm Swift from source when using Carthage.
- The block parameter of
-[RLMRealm transactionWithBlock:]
/Realm.write(_:)
is now marked as__attribute__((noescape))
/@noescape
. - Many forms of queries with key paths on both sides of the comparison operator are now supported.
- Add support for KVC collection operators in
RLMResults
andRLMArray
. - Fail instead of deadlocking in
+[RLMRealm sharedSchema]
, if a Swift property is initialized to a computed value, which attempts to open a Realm on its own.
- Fix poor performance when calling
-[RLMRealm deleteObjects:]
on anRLMResults
which filtered the objects when there are other classes linking to the type of the deleted objects. - An exception is now thrown when defining
Object
properties of an unsupported type.
- Queries are no longer limited to 16 levels of grouping.
- Rework the implementation of encrypted Realms to no longer interfere with debuggers.
- Fix crash when trying to retrieve object instances via
dynamicObjects
. - Throw an exception when querying on a link providing objects, which are from a different Realm.
- Return empty results when querying on a link providing an unattached object.
- Fix crashes or incorrect results when calling
-[RLMRealm refresh]
during fast enumeration. - Add
Int8
support forRealmOptional
,MinMaxType
andAddableType
. - Set the default value for newly added non-optional NSData properties to a zero-byte NSData rather than nil.
- Fix a potential crash when deleting all objects of a class.
- Fix performance problems when creating large numbers of objects with
RLMArray
/List
properties. - Fix memory leak when using Object(value:) for subclasses with
List
orRealmOptional
properties. - Fix a crash when computing the average of an optional integer property.
- Fix incorrect search results for some queries on integer properties.
- Add error-checking for nil realm parameters in many methods such as
+[RLMObject allObjectsInRealm:]
. - Fix a race condition between commits and opening Realm files on new threads that could lead to a crash.
- Fix several crashes when opening Realm files.
-[RLMObject createInRealm:withValue:]
,-[RLMObject createOrUpdateInRealm:withValue:]
, and their variants for the default Realm now always match the contents of anNSArray
against properties in the same order as they are defined in the model.
Prebuilt frameworks are now built with Xcode 7.1.
- Fix ignoring optional properties in Swift.
- Fix CocoaPods installation on case-sensitive file systems.
- Support assigning
Results
toList
properties via KVC. - Honor the schema version set in the configuration in
+[RLMRealm migrateRealm:]
. - Fix crash when using optional Int16/Int32/Int64 properties in Swift.
- No functional changes since beta2.
- Add RLMOptionalBase.h to the podspec.
- CocoaPods v0.38 or greater is now required to install Realm and RealmSwift as pods.
- Functionality common to both
List
andResults
is now declared in aRealmCollectionType
protocol that both types conform to. Results.realm
now returns anOptional<Realm>
in order to conform toRealmCollectionType
, but will always return.Some()
since aResults
cannot exist independently from aRealm
.- Aggregate operations are now available on
List
:min
,max
,sum
,average
. - Committing write transactions (via
commitWrite
/commitWriteTransaction
andwrite
/transactionWithBlock
) now optionally allow for handling errors when the disk is out of space. - Added
isEmpty
property onRLMRealm
/Realm
to indicate if it contains any objects. - The
@count
,@min
,@max
,@sum
and@avg
collection operators are now supported in queries.
- Fix assertion failure when inserting NSData between 8MB and 16MB in size.
- Fix assertion failure when rolling back a migration which removed an object
link or
RLMArray
/List
property. - Add the path of the file being opened to file open errors.
- Fix a crash that could be triggered by rapidly opening and closing a Realm many times on multiple threads at once.
- Fix several places where exception messages included the name of the wrong function which failed.
- Compile iOS Simulator framework architectures with
-fembed-bitcode-marker
. - Fix crashes when the first Realm opened uses a class subset and later Realms opened do not.
- Fix inconsistent errors when
Object(value: ...)
is used to initialize the default value of a property of anObject
subclass. - Throw an exception when a class subset has objects with array or object properties of a type that are not part of the class subset.
- Enable bitcode for iOS and watchOS frameworks.
- Build libraries with Xcode 7 final rather than the GM.
- Add missing KVO handling for moving and exchanging objects in
RLMArray
andList
.
- Setting the primary key property on persisted
RLMObject
s /Object
s via subscripting or key-value coding will cause an exception to be thrown. - Fix crash due to race condition in
RLMRealmConfiguration
where the default configuration was in the process of being copied in one thread, while released in another. - Fix crash when a migration which removed an object or array property is rolled back due to an error.
- The following APIs have been deprecated in favor of the new
RLMRealmConfiguration
class in Realm Objective-C:
Deprecated API | New API |
---|---|
+[RLMRealm realmWithPath:readOnly:error:] |
+[RLMRealm realmWithConfiguration:error:] |
+[RLMRealm realmWithPath:encryptionKey:readOnly:error:] |
+[RLMRealm realmWithConfiguration:error:] |
+[RLMRealm setEncryptionKey:forRealmsAtPath:] |
-[RLMRealmConfiguration setEncryptionKey:] |
+[RLMRealm inMemoryRealmWithIdentifier:] |
+[RLMRealm realmWithConfiguration:error:] |
+[RLMRealm defaultRealmPath] |
+[RLMRealmConfiguration defaultConfiguration] |
+[RLMRealm setDefaultRealmPath:] |
+[RLMRealmConfiguration setDefaultConfiguration:] |
+[RLMRealm setDefaultRealmSchemaVersion:withMigrationBlock] |
RLMRealmConfiguration.schemaVersion and RLMRealmConfiguration.migrationBlock |
+[RLMRealm setSchemaVersion:forRealmAtPath:withMigrationBlock:] |
RLMRealmConfiguration.schemaVersion and RLMRealmConfiguration.migrationBlock |
+[RLMRealm migrateRealmAtPath:] |
+[RLMRealm migrateRealm:] |
+[RLMRealm migrateRealmAtPath:encryptionKey:] |
+[RLMRealm migrateRealm:] |
- The following APIs have been deprecated in favor of the new
Realm.Configuration
struct in Realm Swift for Swift 1.2:
Deprecated API | New API |
---|---|
Realm.defaultPath |
Realm.Configuration.defaultConfiguration |
Realm(path:readOnly:encryptionKey:error:) |
Realm(configuration:error:) |
Realm(inMemoryIdentifier:) |
Realm(configuration:error:) |
Realm.setEncryptionKey(:forPath:) |
Realm(configuration:error:) |
setDefaultRealmSchemaVersion(schemaVersion:migrationBlock:) |
Realm.Configuration.schemaVersion and Realm.Configuration.migrationBlock |
setSchemaVersion(schemaVersion:realmPath:migrationBlock:) |
Realm.Configuration.schemaVersion and Realm.Configuration.migrationBlock |
migrateRealm(path:encryptionKey:) |
migrateRealm(configuration:) |
- The following APIs have been deprecated in favor of the new
Realm.Configuration
struct in Realm Swift for Swift 2.0:
Deprecated API | New API |
---|---|
Realm.defaultPath |
Realm.Configuration.defaultConfiguration |
Realm(path:readOnly:encryptionKey:) throws |
Realm(configuration:) throws |
Realm(inMemoryIdentifier:) |
Realm(configuration:) throws |
Realm.setEncryptionKey(:forPath:) |
Realm(configuration:) throws |
setDefaultRealmSchemaVersion(schemaVersion:migrationBlock:) |
Realm.Configuration.schemaVersion and Realm.Configuration.migrationBlock |
setSchemaVersion(schemaVersion:realmPath:migrationBlock:) |
Realm.Configuration.schemaVersion and Realm.Configuration.migrationBlock |
migrateRealm(path:encryptionKey:) |
migrateRealm(configuration:) |
-
List.extend
in Realm Swift for Swift 2.0 has been replaced withList.appendContentsOf
, mirroring changes toRangeReplaceableCollectionType
. -
Object properties on
Object
subclasses in Realm Swift must be marked as optional, otherwise a runtime exception will be thrown.
- Persisted properties of
RLMObject
/Object
subclasses are now Key-Value Observing compliant. - The different options used to create Realm instances have been consolidated
into a single
RLMRealmConfiguration
/Realm.Configuration
object. - Enumerating Realm collections (
RLMArray
,RLMResults
,List<>
,Results<>
) now enumerates over a copy of the collection, making it no longer an error to modify a collection during enumeration (either directly, or indirectly by modifying objects to make them no longer match a query). - Improve performance of object insertion in Swift to bring it roughly in line with Objective-C.
- Allow specifying a specific list of
RLMObject
/Object
subclasses to include in a given Realm viaRLMRealmConfiguration.objectClasses
/Realm.Configuration.objectTypes
.
- Subscripting on
RLMObject
is now marked as nullable.
- Building for watchOS requires Xcode 7 beta 5.
Object.className
is now marked asfinal
.
- Fix crash when adding a property to a model without updating the schema version.
- Fix unnecessary redownloading of the core library when building from source.
- Fix crash when sorting by an integer or floating-point property on iOS 7.
- None.
- Reduce the amount of memory used by RLMRealm notification listener threads.
- Avoid evaluating results eagerly when filtering and sorting.
- Add nullability annotations to the Objective-C API to provide enhanced compiler warnings and bridging to Swift.
- Make
RLMResult
s andRLMArray
s support Objective-C generics. - Add support for building watchOS and bitcode-compatible apps.
- Make the exceptions thrown in getters and setters more informative.
- Add
-[RLMArray exchangeObjectAtIndex:withObjectAtIndex]
andList.swap(_:_:)
to allow exchanging the location of two objects in the givenRLMArray
/List
. - Added anonymous analytics on simulator/debugger runs.
- Add
-[RLMArray moveObjectAtIndex:toIndex:]
andList.move(from:to:)
to allow moving objects in the givenRLMArray
/List
.
- Processes crashing due to an uncaught exception inside a write transaction will no longer cause other processes using the same Realm to hang indefinitely.
- Fix incorrect results when querying for < or <= on ints that require 64 bits to represent with a CPU that supports SSE 4.2.
- An exception will no longer be thrown when attempting to reset the schema version or encryption key on an open Realm to the current value.
- Date properties on 32 bit devices will retain 64 bit second precision.
- Wrap calls to the block passed to
enumerate
in an autoreleasepool to reduce memory growth when migrating a large amount of objects. - In-memory realms no longer write to the Documents directory on iOS or Application Support on OS X.
- Fixed an issue where the packaged OS X Realm.framework was built with
GCC_GENERATE_TEST_COVERAGE_FILES
andGCC_INSTRUMENT_PROGRAM_FLOW_ARCS
enabled. - Fix a memory leak when constructing standalone Swift objects with NSDate properties.
- Throw an exception rather than asserting when an invalidated object is added to an RLMArray.
- Fix a case where data loss would occur if a device was hard-powered-off shortly after a write transaction was committed which had to expand the Realm file.
- Objects are no longer copied into standalone objects during object creation. This fixes an issue where nested objects with a primary key are sometimes duplicated rather than updated.
- Comparison predicates with a constant on the left of the operator and key path on the right now give correct results. An exception is now thrown for predicates that do not yet support this ordering.
- Fix some crashes in
index_string.cpp
with int primary keys or indexed int properties.
- Schema versions are now represented as
uint64_t
(Objective-C) andUInt64
(Swift) so that they have the same representation on all architectures.
- Swift:
Results
now conforms toCVarArgType
so it can now be passed as an argument toResults.filter(_:...)
andList.filter(_:...)
. - Swift: Made
SortDescriptor
conform to theEquatable
andStringLiteralConvertible
protocols. - Int primary keys are once again automatically indexed.
- Improve error reporting when attempting to mark a property of a type that cannot be indexed as indexed.
- Swift:
RealmSwift.framework
no longer embedsRealm.framework
, which now allows apps using it to pass iTunes Connect validation.
- None.
- Swift: Made
Object.init()
a required initializer. RLMObject
,RLMResults
,Object
andResults
can now be safely deallocated (but still not used) from any thread.- Improve performance of
-[RLMArray indexOfObjectWhere:]
and-[RLMArray indexOfObjectWithPredicate:]
, and implement them for standalone RLMArrays. - Improved performance of most simple queries.
- The interprocess notification mechanism no longer uses dispatch worker threads, preventing it from starving other GCD clients of the opportunity to execute blocks when dozens of Realms are open at once.
- Swift:
Results.average(_:)
now returns an optional, which isnil
if and only if the results set is empty.
- Swift: Added
List.invalidated
, which returns if the givenList
is no longer safe to be accessed, and is analogous to-[RLMArray isInvalidated]
. - Assertion messages are automatically logged to Crashlytics if it's loaded into the current process to make it easier to diagnose crashes.
- Swift: Enumerating through a standalone
List
whose objects themselves have list properties won't crash. - Swift: Using a subclass of
RealmSwift.Object
in an aggregate operator of a predicate no longer throws a spurious type error. - Fix incorrect results for when using OR in a query on a
RLMArray
/List<>
. - Fix incorrect values from
[RLMResults count]
/Results.count
when using!=
on an int property with no other query conditions. - Lower the maximum doubling threshold for Realm file sizes from 128MB to 16MB to reduce the amount of wasted space.
- None.
- Exceptions raised when incorrect object types are used with predicates now contain more detailed information.
- Added
-[RLMMigration deleteDataForClassName:]
andMigration.deleteData(_:)
to enable cleaning up after removing object subclasses
- Prevent debugging of an application using an encrypted Realm to work around frequent LLDB hangs. Until the underlying issue is addressed you may set REALM_DISABLE_ENCRYPTION=YES in your application's environment variables to have requests to open an encrypted Realm treated as a request for an unencrypted Realm.
- Linked objects are properly updated in
createOrUpdateInRealm:withValue:
. - List properties on Objects are now properly initialized during fast enumeration.
- None.
-[RLMRealm inWriteTransaction]
is now public.- Realm Swift is now available on CoocaPods.
- Force code re-signing after stripping architectures in
strip-frameworks.sh
.
- Migration blocks are no longer called when a Realm file is first created.
- The following APIs have been deprecated in favor of newer method names:
Deprecated API | New API |
---|---|
-[RLMMigration createObject:withObject:] |
-[RLMMigration createObject:withValue:] |
-[RLMObject initWithObject:] |
-[RLMObject initWithValue:] |
+[RLMObject createInDefaultRealmWithObject:] |
+[RLMObject createInDefaultRealmWithValue:] |
+[RLMObject createInRealm:withObject:] |
+[RLMObject createInRealm:withValue:] |
+[RLMObject createOrUpdateInDefaultRealmWithObject:] |
+[RLMObject createOrUpdateInDefaultRealmWithValue:] |
+[RLMObject createOrUpdateInRealm:withObject:] |
+[RLMObject createOrUpdateInRealm:withValue:] |
Int8
properties defined in Swift are now treated as integers, rather than booleans.- NSPredicates created using
+predicateWithValue:
are now supported.
- Compound AND predicates with no subpredicates now correctly match all objects.
- Fix issues with removing search indexes and re-enable it.
- Temporarily disable removing indexes from existing columns due to bugs.
- Fix
Extra argument 'objectClassName' in call
errors when building via CocoaPods.
- Migration blocks are no longer called when a Realm file is first created.
RLMCollection
supports collection KVC operations.- Sorting
RLMResults
is 2-5x faster (typically closer to 2x). - Refreshing
RLMRealm
after a write transaction which inserts or modifies strings orNSData
is committed on another thread is significantly faster. - Indexes are now added and removed from existing properties when a Realm file is opened, rather than only when properties are first added.
+[RLMSchema dynamicSchemaForRealm:]
now respects search indexes.+[RLMProperty isEqualToProperty:]
now checks for equalindexed
properties.
- The browser will automatically refresh when the Realm has been modified from another process.
- Allow using Realm in an embedded framework by setting
APPLICATION_EXTENSION_API_ONLY
to YES.
- Fix a crash in CFRunLoopSourceInvalidate.
attributesForProperty:
has been removed fromRLMObject
. You now specify indexed properties by implementing theindexedProperties
method.- An exception will be thrown when calling
setEncryptionKey:forRealmsAtPath:
,setSchemaVersion:forRealmAtPath:withMigrationBlock:
, andmigrateRealmAtPath:
when a Realm at the given path is already open. - Object and array properties of type
RLMObject
will no longer be allowed.
- Add support for sharing Realm files between processes.
- The browser will no longer show objects that have no persisted properties.
RLMSchema
,RLMObjectSchema
, andRLMProperty
now have more useful descriptions.- Opening an encrypted Realm while a debugger is attached to the process no longer throws an exception.
RLMArray
now exposes anisInvalidated
property to indicate if it can no longer be accessed.
- An exception will now be thrown when calling
-beginWriteTransaction
from within a notification triggered by calling-beginWriteTransaction
elsewhere. - When calling
delete:
we now verify that the object being deleted is persisted in the target Realm. - Fix crash when calling
createOrUpdate:inRealm
with nested linked objects. - Use the key from
+[RLMRealm setEncryptionKey:forRealmsAtPath:]
in-writeCopyToPath:error:
and+migrateRealmAtPath:
. - Comparing an RLMObject to a non-RLMObject using
-[RLMObject isEqual:]
or-isEqualToObject:
now returns NO instead of crashing. - Improved error message when an
RLMObject
subclass is defined nested within another Swift declaration. - Fix crash when the process is terminated by the OS on iOS while encrypted realms are open.
- Fix crash after large commits to encrypted realms.
- Improve compatiblity of encrypted Realms with third-party crash reporters.
- Fix incorrect results when using aggregate functions on sorted RLMResults.
- Fix data corruption when using writeCopyToPath:encryptionKey:.
- Maybe fix some assertion failures.
- Fix for crashes when encryption is enabled on 64-bit iOS devices.
- Fix bug that resulted in columns being dropped and recreated during migrations.
- Calling
createInDefaultRealmWithObject:
,createInRealm:withObject:
,createOrUpdateInDefaultRealmWithObject:
orcreateOrUpdateInRealm:withObject:
is a no-op if the argument is an RLMObject of the same type as the receiver and is already backed by the target realm.
- Fix incorrect column type assertions when the first Realm file opened is a read-only file that is missing tables.
- Throw an exception when adding an invalidated or deleted object as a link.
- Throw an exception when calling
createOrUpdateInRealm:withObject:
when the receiver has no primary key defined.
- Fix for RLMObject being treated as a model object class and showing up in the browser.
- Fix compilation from the podspec.
- Fix for crash when calling
objectsWhere:
with grouping in the query onallObjects
.
- Rename
-[RLMRealm encryptedRealmWithPath:key:readOnly:error:]
to-[RLMRealm realmWithPath:encryptionKey:readOnly:error:]
. -[RLMRealm setSchemaVersion:withMigrationBlock]
is no longer global and must be called for each individual Realm path used. You can now call-[RLMRealm setDefaultRealmSchemaVersion:withMigrationBlock]
for the default Realm and-[RLMRealm setSchemaVersion:forRealmAtPath:withMigrationBlock:]
for all others;
- Add
-[RLMRealm writeCopyToPath:encryptionKey:error:]
. - Add support for comparing string columns to other string columns in queries.
- Roll back changes made when an exception is thrown during a migration.
- Throw an exception if the number of items in a RLMResults or RLMArray changes while it's being fast-enumerated.
- Also encrypt the temporary files used when encryption is enabled for a Realm.
- Fixed crash in JSONImport example on OS X with non-en_US locale.
- Fixed infinite loop when opening a Realm file in the Browser at the same time as it is open in a 32-bit simulator.
- Fixed a crash when adding primary keys to older realm files with no primary keys on any objects.
- Fixed a crash when removing a primary key in a migration.
- Fixed a crash when multiple write transactions with no changes followed by a write transaction with changes were committed without the main thread RLMRealm getting a chance to refresh.
- Fixed incomplete results when querying for non-null relationships.
- Improve the error message when a Realm file is opened in multiple processes at once.
- None.
- None.
- Fix an assertion failure when invalidating a Realm which is in a write transaction, has already been invalidated, or has never been used.
- Fix an assertion failure when sorting an empty RLMArray property.
- Fix a bug resulting in the browser never becoming visible on 10.9.
- Write UTF-8 when generating class files from a realm file in the Browser.
- None.
- Improve the error message when a Realm can't be opened due to lacking write permissions.
- Fix an assertion failure when inserting rows after calling
deleteAllObjects
on a Realm. - Separate dynamic frameworks are now built for the simulator and devices to work around App Store submission errors due to the simulator version not being automatically stripped from dynamic libraries.
- None.
- Add support for encrypting Realm files on disk.
- Support using KVC-compliant objects without getters or with custom getter
names to initialize RLMObjects with
createObjectInRealm
and friends.
- Merge native Swift default property values with defaultPropertyValues().
- Don't leave the database schema partially updated when opening a realm fails due to a migration being needed.
- Fixed issue where objects with custom getter names couldn't be used to initialize other objects.
- Fix a major performance regression on queries on string properties.
- Fix a memory leak when circularly linked objects are added to a Realm.
- Deallocating an RLMRealm instance in a write transaction lacking an explicit commit/cancel will now be automatically cancelled instead of committed.
-[RLMObject isDeletedFromRealm]
has been renamed to-[RLMObject isInvalidated]
.
- Add
-[RLMRealm writeCopyToPath:]
to write a compacted copy of the Realm another file. - Add support for case insensitive, BEGINSWITH, ENDSWITH and CONTAINS string queries on array properties.
- Make fast enumeration of
RLMArray
andRLMResults
~30% faster andobjectAtIndex:
~55% faster. - Added a lldb visualizer script for displaying the contents of persisted RLMObjects when debugging.
- Added method
-setDefaultRealmPath:
to change the default Realm path. - Add
-[RLMRealm invalidate]
to release data locked by the current thread.
- Fix for crash when running many simultaneous write transactions on background threads.
- Fix for crashes caused by opening Realms at multiple paths simultaneously which have had properties re-ordered during migration.
- Don't run the query twice when
firstObject
orlastObject
are called on anRLMResults
which has not had its results accessed already. - Fix for bug where schema version is 0 for new Realm created at the latest version.
- Fix for error message where no migration block is specified when required.
- None.
- None.
- Fix browser location in release zip.
- None.
- Added method
-linkingObjectsOfClass:forProperty:
to RLMObject to expose inverse relationships/backlinks.
- Fix for crash due to missing search index when migrating an object with a string primary key in a database created using an older versions (0.86.3 and earlier).
- Throw an exception when passing an array containing a non-RLMObject to -[RLMRealm addObjects:].
- Fix for crash when deleting an object from multiple threads.
- RLMArray has been split into two classes,
RLMArray
andRLMResults
. RLMArray is used for object properties as in previous releases. Moving forward all methods used to enumerate, query, and sort objects return an instance of a new classRLMResults
. This change was made to support diverging apis and the future addition of change notifications for queries. - The api for migrations has changed. You now call
setSchemaVersion:withMigrationBlock:
to register a global migration block and associated version. This block is applied to Realms as needed when opened for Realms at a previous version. The block can be applied manually if desired by callingmigrateRealmAtPath:
. arraySortedByProperty:ascending:
was renamed tosortedResultsUsingProperty:ascending
addObjectsFromArray:
on bothRLMRealm
andRLMArray
has been renamed toaddObjects:
and now accepts any container class which implementsNSFastEnumeration
- Building with Swift support now requires Xcode 6.1
- Add support for sorting
RLMArray
s by multiple columns withsortedResultsUsingDescriptors:
- Added method
deleteAllObjects
onRLMRealm
to clear a Realm. - Added method
createObject:withObject:
onRLMMigration
which allows object creation during migrations. - Added method
deleteObject:
onRLMMigration
which allows object deletion during migrations. - Updating to core library version 0.85.0.
- Implement
objectsWhere:
andobjectsWithPredicate:
for array properties. - Add
cancelWriteTransaction
to revert all changes made in a write transaction and end the transaction. - Make creating
RLMRealm
instances on background threads when an instance exists on another thread take a fifth of the time. - Support for partial updates when calling
createOrUpdateWithObject:
andaddOrUpdateObject:
- Re-enable Swift support on OS X
- Fix exceptions when trying to set
RLMObject
properties after rearranging the properties in aRLMObject
subclass. - Fix crash on IN query with several thousand items.
- Fix crash when querying indexed
NSString
properties. - Fixed an issue which prevented in-memory Realms from being used accross multiple threads.
- Preserve the sort order when querying a sorted
RLMResults
. - Fixed an issue with migrations where if a Realm file is deleted after a Realm is initialized, the newly created Realm can be initialized with an incorrect schema version.
- Fix crash in
RLMSuperSet
when assigning to aRLMArray
property on a standalone object. - Add an error message when the protocol for an
RLMArray
property is not a valid object type. - Add an error message when an
RLMObject
subclass is defined nested within another Swift class.
- Add support for != in queries on object relationships.
- Re-adding an object to its Realm no longer throws an exception and is now a no-op (as it was previously).
- Fix another bug which would sometimes result in subclassing RLMObject subclasses not working.
- Fixed issues with packaging "Realm Browser.app" for release.
- Fix a bug which would sometimes result in subclassing RLMObject subclasses not working.
- Xcode 6 is now supported from the main Xcode project
Realm.xcodeproj
. Xcode 5 is no longer supported.
- Support subclassing RLMObject models. Although you can now persist subclasses, polymorphic behavior is not supported (i.e. setting a property to an instance of its subclass).
- Add support for sorting RLMArray properties.
- Speed up inserting objects with
addObject:
by ~20%. readonly
properties are automatically ignored rather than having to be added toignoredProperties
.- Updating to core library version 0.83.1.
- Return "[deleted object]" rather than throwing an exception when
-description
is called on a deleted RLMObject. - Significantly improve performance of very large queries.
- Allow passing any enumerable to IN clauses rather than just NSArray.
- Add
objectForPrimaryKey:
andobjectInRealm:forPrimaryKey:
convenience methods to fetch an object by primary key.
- Fix error about not being able to persist property 'hash' with incompatible type when building for devices with Xcode 6.
- Fix spurious notifications of new versions of Realm.
- Fix for updating nested objects where some types do not have primary keys.
- Fix for inserting objects from JSON with NSNull values when default values should be used.
- Trying to add a persisted RLMObject to a different Realm now throws an exception rather than creating an uninitialized object.
- Fix validation errors when using IN on array properties.
- Fix errors when an IN clause has zero items.
- Fix for chained queries ignoring all but the last query's conditions.
- Notifications for a refresh being needed (when autorefresh is off) now send the notification type RLMRealmRefreshRequiredNotification rather than RLMRealmDidChangeNotification.
- Updating to core library version 0.83.0.
- Support for primary key properties (for int and string columns). Declaring a property to be the primary key ensures uniqueness for that property for all objects of a given type. At the moment indexes on primary keys are not yet supported but this will be added in a future release.
- Added methods to update or insert (upsert) for objects with primary keys defined.
[RLMObject initWithObject:]
and[RLMObject createInRealmWithObject:]
now support any object type with kvc properties.- The Swift support has been reworked to work around Swift not being supported in Frameworks on iOS 7.
- Improve performance when getting the count of items matching a query but not reading any of the objects in the results.
- Add a return value to
-[RLMRealm refresh]
that indicates whether or not there was anything to refresh. - Add the class name to the error message when an RLMObject is missing a value for a property without a default.
- Add support for opening Realms in read-only mode.
- Add an automatic check for updates when using Realm in a simulator (the checker code is not compiled into device builds). This can be disabled by setting the REALM_DISABLE_UPDATE_CHECKER environment variable to any value.
- Add support for Int16 and Int64 properties in Swift classes.
- Realm change notifications when beginning a write transaction are now sent after updating rather than before, to match refresh.
-isEqual:
now uses the defaultNSObject
implementation unless a primary key is specified for an RLMObject. When a primary key is specified,-isEqual:
calls-isEqualToObject:
and a corresponding implementation for-hash
is also implemented.
- The timer used to trigger notifications has been removed. Notifications are now only triggered by commits made in other threads, and can not currently be triggered by changes made by other processes. Interprocess notifications will be re-added in a future commit with an improved design.
- Updating to core library version 0.82.2.
- Add property
deletedFromRealm
to RLMObject to indicate objects which have been deleted. - Add support for the IN operator in predicates.
- Add support for the BETWEEN operator in link queries.
- Add support for multi-level link queries in predicates (e.g.
foo.bar.baz = 5
). - Switch to building the SDK from source when using CocoaPods and add a Realm.Headers subspec for use in targets that should not link a copy of Realm (such as test targets).
- Allow unregistering from change notifications in the change notification handler block.
- Significant performance improvements when holding onto large numbers of RLMObjects.
- Realm-Xcode6.xcodeproj now only builds using Xcode6-Beta6.
- Improved performance during RLMArray iteration, especially when mutating contained objects.
- Fix crashes and assorted bugs when sorting or querying a RLMArray returned from a query.
- Notifications are no longer sent when initializing new RLMRealm instances on background threads.
- Handle object cycles in -[RLMObject description] and -[RLMArray description].
- Lowered the deployment target for the Xcode 6 projects and Swift examples to iOS 7.0, as they didn't actually require 8.0.
- Support setting model properties starting with the letter 'z'
- Fixed crashes that could result from switching between Debug and Relase builds of Realm.
- Realm-Xcode6.xcodeproj now only builds using Xcode6-Beta5.
- Properties to be persisted in Swift classes must be explicitly declared as
dynamic
. - Subclasses of RLMObject subclasses now throw an exception on startup, rather than when added to a Realm.
- Add support for querying for nil object properties.
- Improve error message when specifying invalid literals when creating or initializing RLMObjects.
- Throw an exception when an RLMObject is used from the incorrect thread rather than crashing in confusing ways.
- Speed up RLMRealm instantiation and array property iteration.
- Allow array and objection relation properties to be missing or null when creating a RLMObject from a NSDictionary.
- Fixed a memory leak when querying for objects.
- Fixed initializing array properties on standalone Swift RLMObject subclasses.
- Fix for queries on 64bit integers.
- Realm-Xcode6.xcodeproj now only builds using Xcode6-Beta4.
- Updating to core library version 0.80.5.
- Now support disabling the
autorefresh
property on RLMRealm instances. - Building Realm-Xcode6 for iOS now builds a universal framework for Simulator & Device.
- Using NSNumber properties (unsupported) now throws a more informative exception.
- Added
[RLMRealm defaultRealmPath]
- Proper implementation for [RLMArray indexOfObjectWhere:]
- The default Realm path on OS X is now ~/Library/Application Support/[bundle identifier]/default.realm rather than ~/Documents
- We now check that the correct framework (ios or osx) is used at compile time.
- Fixed rapid growth of the realm file size.
- Fixed a bug which could cause a crash during RLMArray destruction after a query.
- Fixed bug related to querying on float properties:
floatProperty = 1.7
now works. - Fixed potential bug related to the handling of array properties (RLMArray).
- Fixed bug where array properties accessed the wrong property.
- Fixed bug that prevented objects with custom getters to be added to a Realm.
- Fixed a bug where initializing a standalone object with an array literal would trigger an exception.
- Clarified exception messages when using unsupported NSPredicate operators.
- Clarified exception messages when using unsupported property types on RLMObject subclasses.
- Fixed a memory leak when breaking out of a for-in loop on RLMArray.
- Fixed a memory leak when removing objects from a RLMArray property.
- Fixed a memory leak when querying for objects.
- None.
- Updating to core library version 0.80.3.
- Added support for basic querying of RLMObject and RLMArray properties (one-to-one and one-to-many relationships).
e.g.
[Person objectsWhere:@"dog.name == 'Alfonso'"]
or[Person objectsWhere:@"ANY dogs.name == 'Alfonso'"]
Supports all normal operators for numeric and date types. Does not support NSData properties orBEGINSWITH
,ENDSWITH
,CONTAINS
and other options for string properties. - Added support for querying for object equality in RLMObject and RLMArray properties (one-to-one and one-to-many relationships).
e.g.
[Person objectsWhere:@"dog == %@", myDog]
[Person objectsWhere:@"ANY dogs == %@", myDog]
[Person objectsWhere:@"ANY friends.dog == %@", dog]
Only supports comparing objects for equality (i.e. ==) - Added a helper method to RLMRealm to perform a block inside a transaction.
- OSX framework now supported in CocoaPods.
- Fixed Unicode support in property names and string contents (Chinese, Russian, etc.). Closing #612 and #604.
- Fixed bugs related to migration when properties are removed.
- Fixed keyed subscripting for standalone RLMObjects.
- Fixed bug related to double clicking on a .realm file to launch the Realm Browser (thanks to Dean Moore).
- Rename migration methods to -migrateDefaultRealmWithBlock: and -migrateRealmAtPath:withBlock:
- Moved Realm specific query methods from RLMRealm to class methods on RLMObject (-allObjects: to +allObjectsInRealm: ect.)
- Added +createInDefaultRealmWithObject: method to RLMObject.
- Added support for array and object literals when calling -createWithObject: and -initWithObject: variants.
- Added method -deleteObjects: to batch delete objects from a Realm
- Support for defining RLMObject models entirely in Swift (experimental, see known issues).
- RLMArrays in Swift support Sequence-style enumeration (for obj in array).
- Implemented -indexOfObject: for RLMArray
- Properties other than String, NSData and NSDate require a default value in the model. This can be an empty (but typed) array for array properties.
- The previous caveat also implies that not all models defined in Objective-C can be used for object properties. Only Objective-C models with only implicit (i.e. primitives) or explicit default values can be used. However, any Objective-C model object can be used in a Swift array property.
- Array property accessors don't work until its parent object has been added to a realm.
- Realm-Bridging-Header.h is temporarily exposed as a public header. This is temporary and will be private again once rdar://17633863 is fixed.
- Does not leverage Swift generics and still uses RLM-prefix everywhere. This is coming in #549.
- Rename schemaForObject: to schemaForClassName: on RLMSchema
- Removed -objects:where: and -objects:orderedBy:where: from RLMRealm
- Removed -indexOfObjectWhere:, -objectsWhere: and -objectsOrderedBy:where: from RLMArray
- Removed +objectsWhere: and +objectsOrderedBy:where: from RLMObject
- New Xcode 6 project for experimental swift support.
- New Realm Editor app for reading and editing Realm db files.
- Added support for migrations.
- Added support for RLMArray properties on objects.
- Added support for creating in-memory default Realm.
- Added -objectsWithClassName:predicateFormat: and -objectsWithClassName:predicate: to RLMRealm
- Added -indexOfObjectWithPredicateFormat:, -indexOfObjectWithPredicate:, -objectsWithPredicateFormat:, -objectsWithPredi
- Added +objectsWithPredicateFormat: and +objectsWithPredicate: to RLMObject
- Now allows predicates comparing two object properties of the same type.
Completely rewritten to be much more object oriented.
- Everything
- None.
- None.
The Objective-C API has been updated and your code will break!
RLMTable
objects can only be created with anRLMRealm
object.- Renamed
RLMContext
toRLMTransactionManager
- Renamed
RLMContextDidChangeNotification
toRLMRealmDidChangeNotification
- Renamed
contextWithDefaultPersistence
tomanagerForDefaultRealm
- Renamed
contextPersistedAtPath:
tomanagerForRealmWithPath:
- Renamed
realmWithDefaultPersistence
todefaultRealm
- Renamed
realmWithDefaultPersistenceAndInitBlock
todefaultRealmWithInitBlock
- Renamed
find:
tofirstWhere:
- Renamed
where:
toallWhere:
- Renamed
where:orderBy:
toallWhere:orderBy:
- Added
countWhere:
onRLMTable
- Added
sumOfColumn:where:
onRLMTable
- Added
averageOfColumn:where:
onRLMTable
- Added
minOfProperty:where:
onRLMTable
- Added
maxOfProperty:where:
onRLMTable
- Added
toJSONString
onRLMRealm
,RLMTable
andRLMView
- Added support for
NOT
operator in predicates - Added support for default values
- Added validation support in
createInRealm:withObject:
- None.
TightDB is now Realm! The Objective-C API has been updated and your code will break!
- All references to TightDB have been changed to Realm.
- All prefixes changed from
TDB
toRLM
. TDBTransaction
andTDBSmartContext
have merged intoRLMRealm
.- Write transactions now take an optional rollback parameter (rather than needing to return a boolean).
addColumnWithName:
and variant methods now return the index of the newly created column if successful,NSNotFound
otherwise.
createTableWithName:columns:
has been added toRLMRealm
.- Added keyed subscripting for RLMTable's first column if column is of type RLMPropertyTypeString.
setRow:atIndex:
has been added toRLMTable
.RLMRealm
constructors now have variants that take an writable initialization block- New object interface - tables created/retrieved using
tableWithName:objectClass:
return custom objects
- None.
contextWithPersistenceToFile:error:
renamed tocontextPersistedAtPath:error:
inTDBContext
readWithBlock:
renamed toreadUsingBlock:
inTDBContext
writeWithBlock:error:
renamed towriteUsingBlock:error:
inTDBContext
readTable:withBlock:
renamed toreadTable:usingBlock:
inTDBContext
writeTable:withBlock:error:
renamed towriteTable:usingBlock:error:
inTDBContext
findFirstRow
renamed toindexOfFirstMatchingRow
onTDBQuery
.findFirstRowFromIndex:
renamed toindexOfFirstMatchingRowFromIndex:
onTDBQuery
.- Return
NSNotFound
instead of -1 when appropriate. - Renamed
castClass
tocastToTytpedTableClass
onTDBTable
. removeAllRows
,removeRowAtIndex
,removeLastRow
,addRow
andinsertRow
methods on table now return void instead of BOOL.
- A
TDBTable
can now be queried usingwhere:
andwhere:orderBy:
takingNSPredicate
andNSSortDescriptor
as arguments. - Added
find:
method onTDBTable
to find first row matching predicate. contextWithDefaultPersistence
class method added toTDBContext
. Will create a context persisted to a file in app/documents folder.renameColumnWithIndex:to:
has been added toTDBTable
.distinctValuesInColumnWithIndex
has been added toTDBTable
.dateIsBetween::
,doubleIsBetween::
,floatIsBetween::
andintIsBetween::
have been added toTDBQuery
.- Column names in Typed Tables can begin with non-capital letters too. The generated
addX
selector can look odd. For example, a table with one column with nameage
, appending a new row will look like[table addage:7]
. - Mixed typed values are better validated when rows are added, inserted, or modified as object literals.
addRow
,insertRow
, and row updates can be done using objects derived fromNSObject
.where
has been added toTDBView
andTDBViewProtocol
.- Adding support for "smart" contexts (
TDBSmartContext
).
- Modifications of a
TDBView
andTDBQuery
now throw an exception in a readtransaction.
The Objective-C API has been updated and your code will break!
Of notable changes a fast interface has been added.
This interface includes specific methods to get and set values into Tightdb.
To use these methods import <Tightdb/TightdbFast.h>
.
getTableWithName:
renamed totableWithName:
inTDBTransaction
.addColumnWithName:andType:
renamed toaddColumnWithName:type:
inTDBTable
.columnTypeOfColumn:
renamed tocolumnTypeOfColumnWithIndex
inTDBTable
.columnNameOfColumn:
renamed tonameOfColumnWithIndex:
inTDBTable
.addColumnWithName:andType:
renamed toaddColumnWithName:type:
inTDBDescriptor
.- Fast getters and setters moved from
TDBRow.h
toTDBRowFast.h
.
- Added
minDateInColumnWithIndex
andmaxDateInColumnWithIndex
toTDBQuery
. - Transactions can now be started directly on named tables.
- You can create dynamic tables with initial schema.
TDBTable
andTDBView
now have a shared protocol so they can easier be used interchangeably.
- Fixed bug in 64 bit iOS when inserting BOOL as NSNumber.
- Typed interface Cursor has now been renamed to Row.
- TDBGroup has been renamed to TDBTransaction.
- Header files are renamed so names match class names.
- Underscore (_) removed from generated typed table classes.
- TDBBinary has been removed; use NSData instead.
- Underscope (_) removed from generated typed table classes.
- Constructor for TDBContext has been renamed to contextWithPersistenceToFile:
- Table findFirstRow and min/max/sum/avg operations has been hidden.
- Table.appendRow has been renamed to addRow.
- getOrCreateTable on Transaction has been removed.
- set*:inColumnWithIndex:atRowIndex: methods have been prefixed with TDB
- *:inColumnWithIndex:atRowIndex: methods have been prefixed with TDB
- addEmptyRow on table has been removed. Use [table addRow:nil] instead.
- TDBMixed removed. Use id and NSObject instead.
- insertEmptyRow has been removed from table. Use insertRow:nil atIndex:index instead.
- Added firstRow, lastRow selectors on view.
- firstRow and lastRow on table now return nil if table is empty.
- getTableWithName selector added on group.
- getting and creating table methods on group no longer take error argument.
- [TDBQuery parent] and [TDBQuery subtable:] selectors now return self.
- createTable method added on Transaction. Throws exception if table with same name already exists.
- Experimental support for pinning transactions on Context.
- TDBView now has support for object subscripting.
- None.
The Objective-C API has been updated and your code will break!
- Most selectors have been renamed in the binding!
- Prepend TDB-prefix on all classes and types.
- Return types and parameters changed from size_t to NSUInteger.
- Adding setObject to TightdbTable (t[2] = @[@1, @"Hello"] is possible).
- Adding insertRow to TightdbTable.
- Extending appendRow to accept NSDictionary.
- None.
The Objective-C API has been updated and your code will break!
- addRow renamed to addEmptyRow
- Adding a simple class for version numbering.
- Adding get-version and set-version targets to build.sh.
- tableview now supports sort on column with column type bool, date and int
- tableview has method for checking the column type of a specified column
- tableview has method for getting the number of columns
- Adding methods getVersion, getCoreVersion and isAtLeast.
- Adding appendRow to TightdbTable.
- Adding object subscripting.
- Adding method removeColumn on table.
- None.