Realm is a mobile database: a replacement for SQLite & ORMs
APACHE-2.0 License
Bot releases are hidden (Show)
Published by nirinchev over 3 years ago
This release changes the way Unity binaries are packaged and obviates the need to have an extra Unity package that contains the dependencies as standalone modules. If you were using the io.realm.unity-bundled
package, please remove it and add the newly released io.realm.unity
one.
No RealmObjects. Has linker stripped them?
. Now, the weaving errors will show up on every code change/weave attempt and the runtime error will explicitly suggest manually re-running the weaver. (Issue #2310)Published by nirinchev over 3 years ago
This release adds SDK support for four new datatatypes - Guid
, RealmValue
, ISet<TValue>
, and IDictionary<string, TValue>
.
NOTE: This version upgrades the Realm file format version to add support for the new data types and to adjust how primary keys are handled. Realm files opened will be automatically upgraded and cannot be read by versions older than v10.2.0. This upgrade should be a fairly fast one. Note that we now automatically create a backup of the pre-upgrade Realm.
Add support for the Guid
data type. It can be used as primary key and is indexable. (PR #2120)
Add support for dictionaries. Currently only string keys are supported, while the value type may be any of the supported types (the primitive types, RealmValue
, or custom types that inherit from RealmObject/EmbeddedObject). Lists, sets, or other dictionaries may not be used as the value type. To add a dictionary to your model, define a getter-only property of type IDictionary<string, T>
:
public class MyObject : RealmObject
{
public IDictionary<string, decimal> Denominations { get; }
}
// Realm will automatically manage the underlying dictionary, so there's no need
// to define a constructor or assign it to some value.
var obj = new MyObject();
obj.Denominations.Add("quarter", 0.25d);
Add support for RealmValue
data type. This new type can represent any valid Realm data type, including objects. Collections (lists, sets and dictionaries) of RealmValue
are also supported, but RealmValue
itself cannot contain collections. Please note that a property of type RealmValue
cannot be nullable, but can contain null, represented by the value RealmValue.Null
. (PR #2252)
public class MyObject : RealmObject
{
public RealmValue MyValue { get; set; }
public IList<RealmValue> ValuesList { get; }
public ISet<RealmValue> ValuesSet { get; }
public IDictionary<string, RealmValue> ValuesDict { get; }
}
var obj = new MyObject();
obj.MyValue = RealmValue.Null;
obj.MyValue = 1;
obj.MyValue = "abc";
if (obj.MyValue.Type == RealmValueType.String)
{
var myString = obj.MyValue.AsString();
}
Add support for sets of objects or primitive values. Sets are unordered collections that ensure uniqueness of their elements. Realm uses its internal equality comparer and it is not possible to customize its behavior by overriding Equals
or GetHashCode
on your custom classes. Objects will always be compared by db reference - i.e. two distinct objects in the database will always be different, even if their contents are identical, and multiple references to the same database object will always be equal.
public class MyObject : RealmObject
{
public ISet<string> UniqueStrings { get; }
}
// Realm will automatically manage the underlying set, so there's no need
// to define a constructor or assign it to some value.
var obj = new MyObject();
var didAdd = obj.UniqueStrings.Add("foo"); // true
didAdd = obj.UniqueStrings.Add("foo"); // false
Added support for value substitution in string based queries. This enables expressions following this syntax: realm.All<T>().Filter("field1 = $0 && field2 = $1", 123, "some-string-value")
. (Issue #1822)
Reduced the size of the native binaries by ~5%. (PR #2239)
Added a new class - Logger
, which allows you to override the default logger implementation (previously writing to stdout
or stderr
) with a custom one by setting Logger.Default
. This replaces AppConfiguration.CustomLogger
and AppConfiguration.LogLevel
which will be removed in a future release. The built-in implementations are:
Console
- uses the System.Console
for most projects and UnityEngine.Debug
for Unity projects: Logger.Default = Logger.Console;
Null
- ignores all messages: Logger.Default = Logger.Null;
Function
- proxies calls to a supplied function: Logger.Default = Logger.Function(message => myExternalLogger.Log(message));
Custom loggers can derive from the Logger
class and provide their own implementation for the Log
method or use Function
and provide an Action<string>
. (PR #2276)
RealmObjectBase
now correctly overrides and implements GetHashCode()
. (Issue #1650)
Added an override of RealmObject.ToString()
to output more meaningful information about the object content. It will output the type of the object, the primary key (if one is defined), as well as information whether the object is managed or deleted. (Issue #2347)
Added new API for dynamically accessing object properties. These are designed to support ahead-of-time compiled platforms, such as Xamarin.iOS and Unity with IL2CPP compilation. The
intention is to eventually make these the default API, while also supporting the legacy DLR-based API. Example:
// Make sure to cast away the dynamic immediately on AOT platforms.
var people = (IQueryable<RealmObject>)realm.DynamicApi.All("Person");
foreach (var person in people)
{
var firstName = person.DynamicApi.Get<string>("FirstName");
var address = person.DynamicApi.Get<EmbeddedObject>("Address");
var city = address.DynamicApi.Get<string>("City");
}
// When casting a dynamic object, always cast first to object and then
// to the actual object type to remove any callsites being generated.
var newPerson = (RealmObject)(object)realm.DynamicApi.Create("Person", 123);
newPerson.DynamicApi.Set("FirstName", "Peter");
Added a Unity Editor option to enable weaving editor assemblies. This should be "off" unless your project has Editor assemblies that reference Realm - for example, an EditMode test assembly that tests Realm-related functionality. Keeping it "on" may slow down builds a little as more assemblies will need to be evaluated for weaving. (Issue #2346)
We now make a backup of the realm file prior to any file format upgrade. The backup is retained for 3 months. Backups from before a file format upgrade allows for better analysis of any upgrade failure. We also restore a backup, if a) an attempt is made to open a realm file whith a "future" file format and b) a backup file exist that fits the current file format. (#4166)
OrderBy
clauses on a query would result in the clauses being appended to each other as if they were .ThenBy
rather than the last clause replacing the preceding ones. (PR #2255)SyncConfiguration.ObjectTypes
, added a check to validate the schema and ensure all EmbeddedObject
classes are reachable from a class inheriting from RealmObject
. More info about this subject can be found here. (PR #2259)Undefined symbols for architecture xxx: "_realm_thread_safe_reference_destroy"
when building a Unity project for iOS. (Issue #2318)RealmInteger
values. This has never been supported, but previously it would fail silently whereas now it'll be a compile time error. (Issue #2308)NullReferenceException
to be thrown if you set SyncConfiguration.OnProgress
to null
shortly after calling Realm.GetInstanceAsync(syncConfig)
. (Issue #2400)Failed to parse, or apply received changeset: ERROR: ArrayInsert: Invalid prior_size (list size = 4, prior_size = 0)
(Issue #4740
The Unity packages are very early previews and are considered unstable. We do not recommend using them in production because issues are expected.
Published by nirinchev over 3 years ago
Invalid ref translation entry [0, 78187493520]
. (Core upgrade)!m_notifier_skip_version.version
or m_notifier_sg->get_version() + 1 == new_version.version
when performing writes inside change notification callbacks. (Core upgrade)ERROR: Connection[1]: Websocket: Expected HTTP response 101 Switching Protocols, but received: HTTP/1.1 401 Unauthorized
. (Core upgrade)uncaught exception in notifier thread: N5realm11KeyNotFoundE: No such object
. This could happen in a synchronized app when a linked object was deleted by another client. (Core upgrade)ThreadSafeReference
to a readonly Realm would result in a crash. (Core upgrade)The Unity packages are very early previews and are considered unstable. We do not recommend using them in production because issues are expected, especially when compiling with IL2CPP.
Published by papafe over 3 years ago
Undefined symbols for architecture xxx: "_realm_thread_safe_reference_destroy"
when building a Unity project for iOS. (Issue #2318)RealmInteger
values. This has never been supported, but previously it would fail silently whereas now it'll be a compile time error. (Issue #2308)RealmObject.ToString()
to output more meaningful information about the object content. It will output the type of the object, the primary key (if one is defined), as well as information whether the object is managed or deleted. (Issue #2347)The Unity packages are very early previews and are considered unstable. We do not recommend using them in production because issues are expected, especially when compiling with IL2CPP.
Published by papafe over 3 years ago
"Access violation"
error being thrown when using sync on Windows.The Unity packages are very early previews and are considered unstable. We do not recommend using them in production because issues are expected, especially when compiling with IL2CPP.
Published by nirinchev over 3 years ago
This beta release introduces support for 4 new datatypes - Guid
, ISet<T>
, IDictionary<string, T>
, and RealmValue
. It also includes multiple bug fixes for our Unity packages, so if you're alpha testing the Unity releases, it is strongly recommended that you upgrade to this version.
Downgrading to an earlier version of the Realm SDK is not supported, so it is strongly recommended that you do not publish production apps using beta versions of the SDK.
This release is incompatible with Stable versions of Realm Studio. A compatible beta version of Realm Studio is coming soon.
Unity binaries are provided with this release as a very early preview. We don't officially support Unity as a platform yet, so it is expected that there are bugs and missing functionality.
__C_specific_handler
) being used. (Issue #2235)OrderBy
clauses on a query would result in the clauses being appended to each other as if they were .ThenBy
rather than the last clause replacing the preceding ones. (PR #2255)SyncConfiguration.ObjectTypes
, added a check to validate the schema and ensure all EmbeddedObject
classes are reachable from a class inheriting from RealmObject
. More info about this subject can be found here. (PR #2259)Add support for the Guid
data type. It can be used as primary key and is indexable. (PR #2120)
Add support for dictionaries. Currently only string keys are supported, while the value
type may be any of the supported types (the primitive types or custom types that inherit
from RealmObject/EmbeddedObject). Lists, sets, or other dictionaries may not be used as
the value type. To add a dictionary to your model, define a getter-only property of type
IDictionary<string, T>
:
public class MyObject : RealmObject
{
public IDictionary<string, decimal> Denominations { get; }
}
// Realm will automatically manage the underlying dictionary, so there's no need
// to define a constructor or assign it to some value.
var obj = new MyObject();
obj.Denominations.Add("quarter", 0.25d);
Add support for RealmValue
data type. This new type can represent any valid Realm data type, including objects. Collections (lists, sets and dictionaries) of RealmValue
are also supported, but 'RealmValue' cannot contain collections. Please note that a property of type RealmValue
cannot be nullable, but can contain null, represented by the value RealmValue.Null
. (PR #2252)
public class MyObject : RealmObject
{
public RealmValue MyValue { get; set; }
public IList<RealmValue> ValuesList { get; }
public ISet<RealmValue> ValuesSet { get; }
public IDictionary<string, RealmValue> ValuesDict { get; }
}
var obj = new MyObject();
obj.MyValue = RealmValue.Null;
obj.MyValue = 1;
obj.MyValue = "abc";
if (obj.Type == RealmValueType.String)
{
var myString = obj.MyValue.AsString();
}
Add support for sets of objects or primitive values. Sets are unordered collections that ensure uniqueness of their elements. Realm uses its internal equality comparer
and it is not possible to customize its behavior by overriding Equals
or GetHashCode
on your custom classes. Objects will always be compared by db reference - i.e.
two distinct objects in the database will always be different, even if their contents are identical, and multiple references to the same database object will always be
equal.
public class MyObject : RealmObject
{
public ISet<string> UniqueStrings { get; }
}
// Realm will automatically manage the underlying set, so there's no need
// to define a constructor or assign it to some value.
var obj = new MyObject();
var didAdd = obj.UniqueStrings.Add("foo"); // true
didAdd = obj.UniqueStrings.Add("foo"); // false
Added support for value substitution in string based queries. This enables expressions following this syntax: realm.All<T>().Filter("field1 = $0 && field2 = $1", 123, "some-string-value")
. (Issue #1822)
Reduced the size of the native binaries by ~5%. (PR #2239)
Added a new class - Logger
, which allows you to override the default logger implementation (previously writing to stdout
or stderr
) with a custom one by setting
Logger.Default
. This replaces AppConfiguration.CustomLogger
and AppConfiguration.LogLevel
which will be removed in a future release. The built-in implementations are:
Console
- uses the System.Console
for most projects and UnityEngine.Debug
for Unity projects: Logger.Default = Logger.Console;
Null
- ignores all messages: Logger.Default = Logger.Null;
Function
- proxies calls to a supplied function: Logger.Default = Logger.Function(message => myExternalLogger.Log(message));
Custom loggers can derive from the Logger
class and provide their own implementation for the Log
method or use Function
and provide an Action<string>
. (PR #2276)
RealmObjectBase
now correctly overrides and implements GetHashCode()
. (Issue #1650)
The Unity packages are very early previews and are considered unstable. We do not recommend using them in production because issues are expected, especially when compiling with IL2CPP.
Published by nirinchev over 3 years ago
"Assertion failed: !fields.has_missing_parent_update()"
. (Core upgrade)"Assertion failed: cx.w[1] == 0"
. (Core upgrade)The Unity packages are very early previews and are considered unstable. We do not recommend using them in production because issues are expected, especially when compiling with IL2CPP.
Published by nirinchev over 3 years ago
__C_specific_handler
) being used. (Issue #2235)The Unity packages are very early previews and are considered unstable. We do not recommend using them in production because issues are expected, especially when compiling with IL2CPP.
Published by nirinchev over 3 years ago
Assertion failed: lo() <= std::numeric_limits<uint32_t>::max()
. (Core upgrade)Published by LaPeste over 3 years ago
Assertion failed: ref + size <= next->first
. (Core upgrade)Published by nirinchev over 3 years ago
This is the first stable release from the v10 line of releases - the changelog includes all changes introduced between 10.0.0-beta.1 through beta.6. It adds multiple improvements to the local database as well as support for synchronizing with MongoDB Realm Cloud (https://realm.mongodb.com). It no longer supports legacy Realm Cloud (https://cloud.realm.io), so users who haven't migrated to MongoDB Realm should not upgrade.
SyncSubscription
types. (#2011)Realm
class to Realm.DynamicApi
:
Realm.CreateObject(string className, object primaryKey)
is now Realm.DynamicApi.CreateObject(string className, object primaryKey)
.Realm.All(string className)
is now Realm.DynamicApi.All(string className)
.Realm.RemoveAll(string className)
is now Realm.DynamicApi.RemoveAll(string className)
.Realm.Find(string className, long? primaryKey)
is now Realm.DynamicApi.Find(string className, long? primaryKey)
.Realm.Find(string className, string primaryKey)
is now Realm.DynamicApi.Find(string className, string primaryKey)
._id
. You can use the MapTo("_id")
attribute to avoid using unidiomatic names for the model properties.FullSyncConfiguration
to SyncConfiguration
.RealmObject.FreezeInPlace
. To freeze a realm object use the Freeze
extension method. (Issue #2180)Added support for syncing to MongoDB instead of Realm Object Server. Applications must be created at realm.mongodb.com.
Added an App
class which is the entrypoint for synchronizing with a MongoDB Realm App.
Added User.CustomData
containing an unstructured document with additional information about the user. Custom data is configured in your MongoDB Realm App.
Added User.Functions
. This is the entry point for calling Remote MongoDB Realm functions. Functions allow you to define and execute server-side logic for your application. Functions are written in modern JavaScript (ES6+) and execute in a serverless manner. When you call a function, you can dynamically access components of the current application as well as information about the request to execute the function and the logged in user that sent the request.
Added User.GetMongoClient
exposing an API for CRUD operations on a Remote MongoDB Service.
Added User.GetPushClient
exposing an API for registering a device for push notifications.
Change SyncConfiguration
to accept partition value instead of a server Uri. Partition values can currently be of types string
, long
, or ObjectId
. Opening a realm by partition value is the equivalent of previously opening a realm by URL. In this case, partitions are meant to be more closely associated with your data. E.g., if you are a large retailer with multiple locations, the partition key can be the store Id and you each Realm will only contain data related to the specified store.
Add support for the Decimal128 data type. This is a 128-bit IEEE 754 decimal floating point number. Properties of this type can be declared either as MongoDB.Bson.Decimal128
type or the built-in decimal
type. Note that .NET's built-in decimal is 96-bit, so it cannot represent the full range of numbers, representable by Decimal128
. (PR #2014)
Add support for the ObjectId
data type. This is a 12 byte unique identifier that is common as a document id in MongoDB databases. It can be used as primary key. (PR #2035)
Add support for embedded objects. Embedded objects are objects which are owned by a single parent object, and are deleted when that parent object is deleted or their parent no longer references them. Embedded objects are declared by subclassing EmbeddedObject
instead of RealmObject
. Reassigning an embedded object is not allowed and neither is linking to it from multiple parents. Querying for embedded objects directly is also disallowed as they should be viewed as complex structures belonging to their parents as opposed to standalone objects. A trivial example is:
public class Address : EmbeddedObject
{
public string Street { get; set; }
public string City { get; set; }
}
public class Person : RealmObject
{
public string Name { get; set; }
// Address is an embedded object - you reference it as usual
public Address Address { get; set; }
}
public class Company : RealmObject
{
public string PhoneNumber { get; set; }
// Embedded objects can be contained in lists too
public IList<Address> OfficeAddresses { get; }
}
Added new dynamic methods for instantiating embedded objects:
Realm.DynamicApi.CreateEmbeddedObjectForProperty
should be used to create an embedded object and assign it to a parent's property. For example:
// static API
var person = new Person();
person.Address = new Address
{
City = "New York"
};
// dynamic API
var dynamicPerson = realm.DynamicApi.CreateObject("Person");
var address = realm.DynamicApi.CreateEmbeddedObjectForProperty(dynamicPerson, "Address")
address.City = "New York";
Realm.DynamicApi.AddEmbeddedObjectToList
should be used to create an embedded object and add it to a parent's list property.
Realm.DynamicApi.InsertEmbeddedObjectInList
should be used to create an embedded object and insert it in a parent's list property at a specified index.
Realm.DynamicApi.SetEmbeddedObjectInList
should be used to create an embedded object and set it at an index in a parent's list property.
// static API
var company = new Company();
company.OfficeAddresses.Add(new Address
{
City = "New York"
});
company.OfficeAddresses.Insert(0, new Address
{
City = "Palo Alto"
});
company.OfficeAddresses[1] = new Address
{
City = "New Jersey"
};
// dynamic API
var dynamicCompany = realm.DynamicApi.CreateObject("Company");
var officeToAdd = realm.DynamicApi.AddEmbeddedObjectToList(dynamicCompany.OfficeAddresses);
officeToAdd.City = "New York";
var officeToInsert = realm.DynamicApi.InsertEmbeddedObjectInList(dynamicCompany.OfficeAddresses, 0);
officeToInsert.City = "Palo Alto";
var officeToSet = realm.DynamicApi.SetEmbeddedObjectInList(dynamicCompany.OfficeAddresses, 1);
officeToSet.City = "New Jersey";
The memory mapping scheme for Realm files has changed to better support opening very large files.
Replaced the implementation of the string query parser (the one used for realm.All().Filter("some-string-query")
). This results in ~5% reduction of the size of the native binary while keeping the query execution times on par with the old parser. (PR #2185, Core upgrade)
Optimized the internal code that handles conversions between types. This should result in a minor performance increase
for most data operations that should be most noticeable on Ahead-of-Time compiled platforms, such as iOS/UWP. Due to the
nature of the change, it's possible that conversions that previously happened automatically when working with dynamic objects
no longer do. If you encounter a NotSupportedException
with the message No conversion exists from *type A* to *type B*
and believe this is a bug, please open a Github Issue. (PR #2149)
Added an extra compile-time check to detect erroneous List declarations and suggest IList for collection properties in Realm objects. (Issue #2083)
Added overloads for Realm.Write
and Realm.WriteAsync
that can return a value. (Issue #2081)
Incompatible MarshalAs detected in parameter named 'value'. Please refer to MCG's warning message for more information.
. (Issue #2169)foo.Name
could return foo.Bar
. This could only happen when using thePublished by nirinchev over 3 years ago
DateTimeOffset
values. (PR #2200)Published by nirinchev almost 4 years ago
This version has a serious regression related to reading and writing date properties. It stores dates in an incorrect format at the database layer, which means that values written in earlier versions will be read incorrectly (typically values very close to 0000-01-01
) and values written with this version will be read incorrectly with future versions.
This is primarily a bug fix release that addresses an SSL regression in beta.3 and fixes a long standing bug with multiprocess support on Windows. There is no public beta.4 release, so beta.5 follows immediately after beta.3.
RealmObject.FreezeInPlace
. To freeze a realm object use the Freeze
extension method. (Issue #2180)Incompatible MarshalAs detected in parameter named 'value'. Please refer to MCG's warning message for more information.
. (Issue #2169)SSL server certificate rejected
. (Core upgrade)realm.All().Filter("some-string-query")
). This results in ~5% reduction of the size of the native binary while keeping the query execution times on par with the old parser. (PR #2185, Core upgrade)Starting with beta.5, we're publishing very early prerelease bundles of a Unity-compatible package. These are in no way supported and we strongly advise against using them in production. That being said, we will respond to and address issues and plan to ship fully-fledged and supported Unity package at a later point.
To install the Unity package, open the Unity Package Manager and select the Add package from tarball option. The two packages we publish are:
realm.unity-*version*.tgz
: this package contains the Realm precompiled .dll as well as all the native binaries for all platforms. It doesn't include any of the managed dependencies, such as MongoDB.Bson
or Remotion.Linq
. It's up to the developer to satisfy those dependencies with versions equal to or newer than the versions listed on NuGet (Note that Fody
and Realm.Fody
are not dependencies of the Unity package and don't need to be installed).realm.unity.bundle-*version*.tgz
: this package contains everything in the first one + all the managed dependencies at their correct versions. This is the easiest package to get started with, but may introduce conflicts in case your project already bundles a dependency that Realm brings in, such as System.Buffers
or MongoDB.Bson
.Published by nirinchev almost 4 years ago
Credentials.Google(string)
now has an additional argument of type GoogleCredentialType
. The available types are IdToken
and AuthCode
and specify what type of credential the passed string represents.foo.Name
could return foo.Bar
. This could only happen when using the dynamic API during a migration and does not affect apps that use the strongly typed API or run on platforms other than .NET Core 3.x/.NET 5.n != realm::npos
when integrating changesets from the server. (Core upgrade)NotSupportedException
with the message No conversion exists from *type A* to *type B*
and believe this is a bug, please open a Github Issue. (PR #2149)Published by nirinchev almost 4 years ago
Realm.Write
and Realm.WriteAsync
that can return a value. (Issue #2081)Published by nirinchev almost 4 years ago
Realm accessed from incorrect thread
exception being thrown when accessing a Realm instance on the main thread in UWP apps. (Issue #2045)Published by nirinchev about 4 years ago
This beta release adds multiple improvements to the local database as well as support for synchronizing with MongoDB Realm Cloud. It no longer supports legacy Realm Cloud (https://cloud.realm.io), so users who haven't migrated to MongoDB Realm should not upgrade.
SyncSubscription
types. (#2011)Realm
class to Realm.DynamicApi
:
Realm.CreateObject(string className, object primaryKey)
is now Realm.DynamicApi.CreateObject(string className, object primaryKey)
.Realm.All(string className)
is now Realm.DynamicApi.All(string className)
.Realm.RemoveAll(string className)
is now Realm.DynamicApi.RemoveAll(string className)
.Realm.Find(string className, long? primaryKey)
is now Realm.DynamicApi.Find(string className, long? primaryKey)
.Realm.Find(string className, string primaryKey)
is now Realm.DynamicApi.Find(string className, string primaryKey)
._id
. You can use the MapTo("_id")
attribute to avoid using unidiomatic names for the model properties.FullSyncConfiguration
to SyncConfiguration
.Added support for syncing to MongoDB instead of Realm Object Server. Applications must be created at realm.mongodb.com.
Added an App
class which is the entrypoint for synchronizing with a MongoDB Realm App.
Added User.CustomData
containing an unstructured document with additional information about the user. Custom data is configured in your MongoDB Realm App.
Added User.Functions
. This is the entry point for calling Remote MongoDB Realm functions. Functions allow you to define and execute server-side logic for your application. Functions are written in modern JavaScript (ES6+) and execute in a serverless manner. When you call a function, you can dynamically access components of the current application as well as information about the request to execute the function and the logged in user that sent the request.
Added User.GetMongoClient
exposing an API for CRUD operations on a Remote MongoDB Service.
Added User.GetPushClient
exposing an API for registering a device for push notifications.
Change SyncConfiguration
to accept partition value instead of a server Uri. Partition values can currently be of types string
, long
, or ObjectId
. Opening a realm by partition value is the equivalent of previously opening a realm by URL. In this case, partitions are meant to be more closely associated with your data. E.g., if you are a large retailer with multiple locations, the partition key can be the store Id and you each Realm will only contain data related to the specified store.
Add support for the Decimal128 data type. This is a 128-bit IEEE 754 decimal floating point number. Properties of this type can be declared either as MongoDB.Bson.Decimal128
type or the built-in decimal
type. Note that .NET's built-in decimal is 96-bit, so it cannot represent the full range of numbers, representable by Decimal128
. (PR #2014)
Add support for the ObjectId
data type. This is a 12 byte unique identifier that is common as a document id in MongoDB databases. It can be used a primary key. (PR #2035)
Add support for embedded objects. Embedded objects are objects which are owned by a single parent object, and are deleted when that parent object is deleted or their parent no longer references them. Embedded objects are declared by subclassing EmbeddedObject
instead of RealmObject
. Reassigning an embedded object is not allowed and neither is linking to it from multiple parents. Querying for embedded objects directly is also disallowed as they should be viewed as complex structures belonging to their parents as opposed to standalone objects. A trivial example is:
public class Address : EmbeddedObject
{
public string Street { get; set; }
public string City { get; set; }
}
public class Person : RealmObject
{
public string Name { get; set; }
// Address is an embedded object - you reference it as usual
public Address Address { get; set; }
}
public class Company : RealmObject
{
public string PhoneNumber { get; set; }
// Embedded objects can be contained in lists too
public IList<Address> OfficeAddresses { get; }
}
Added new dynamic methods for instantiating embedded objects:
Realm.DynamicApi.CreateEmbeddedObjectForProperty
should be used to create an embedded object and assign it to a parent's property. For example:
// static API
var person = new Person();
person.Address = new Address
{
City = "New York"
};
// dynamic API
var dynamicPerson = realm.DynamicApi.CreateObject("Person");
var address = realm.DynamicApi.CreateEmbeddedObjectForProperty(dynamicPerson, "Address")
address.City = "New York";
Realm.DynamicApi.AddEmbeddedObjectToList
should be used to create an embedded object and add it to a parent's list property.
Realm.DynamicApi.InsertEmbeddedObjectInList
should be used to create an embedded object and insert it in a parent's list property at a specified index.
Realm.DynamicApi.SetEmbeddedObjectInList
should be used to create an embedded object and set it at an index in a parent's list property.
// static API
var company = new Company();
company.OfficeAddresses.Add(new Address
{
City = "New York"
});
company.OfficeAddresses.Insert(0, new Address
{
City = "Palo Alto"
});
company.OfficeAddresses[1] = new Address
{
City = "New Jersey"
};
// dynamic API
var dynamicCompany = realm.DynamicApi.CreateObject("Company");
var officeToAdd = realm.DynamicApi.AddEmbeddedObjectToList(dynamicCompany.OfficeAddresses);
officeToAdd.City = "New York";
var officeToInsert = realm.DynamicApi.InsertEmbeddedObjectInList(dynamicCompany.OfficeAddresses, 0);
officeToInsert.City = "Palo Alto";
var officeToSet = realm.DynamicApi.SetEmbeddedObjectInList(dynamicCompany.OfficeAddresses, 1);
officeToSet.City = "New Jersey";
The memory mapping scheme for Realm files has changed to better support opening very large files.
Published by nirinchev about 4 years ago
Published by nirinchev about 4 years ago
Published by nirinchev about 4 years ago
NOTE: This version bumps the Realm file format to version 11. It is not possible to downgrade to version 10 or earlier. Files created with older versions of Realm will be automatically upgraded. Only Realm Studio 5.0.0 or later will be able to open the new file format.
Realm.Freeze()
, RealmObject.Freeze()
, RealmObject.FreezeInPlace()
, IQueryable<RealmObject>.Freeze()
, IList<T>.Freeze()
, and IRealmCollection<T>.Freeze()
. These methods will produce the frozen version of the instance on which they are called.Realm.IsFrozen
, RealmObject.IsFrozen
, and IRealmCollection<T>.IsFrozen
, which returns whether or not the data is frozen.RealmConfigurationBase.MaxNumberOfActiveVersions
. Setting this will cause Realm to throw an exception if too many versions of the Realm data are live at the same time. Having too many versions can dramatically increase the filesize of the Realm.SynchronizationContext
-confined Realms. Rather than being bound to a specific thread, queue-confined Realms are bound to a SynchronizationContext
, regardless of whether it dispatches work on the same or a different thread. Opening a Realm when SynchronizationContext.Current
is null - most notably Task.Run(...)
- will still confine the Realm to the thread on which it was opened.Access to invalidated List object
being thrown when adding objects to a list while at the same time deleting the object containing the list. (Issue #1971).ElementAt()
on a query where a string filter with a sort clause was applied. (PR #2002)