NonTransactionalReads is a specific Session option that allows to read once fetched entities right from Session cache without the requirement to have an open transaction. This mode might be useful for desktop application that have only one Session instance for the entire lifetime of application or for services like auditing, logging, etc. that need to read persistent fields without having any idea of sessions, transactions, etc.
To demonstrate the approach, let's start with a sample. Here is the persistent class with one lazy loading field:
In DataObjects.Net 5.0 you can do this in a more comfortable way using the new NonTransactionalReads flag.
What is more interesting, the same behavior can be achieved without using any transactions at all. Let's re-write the sample:
So, the key points of the NonTransactionalReads mode:
To demonstrate the approach, let's start with a sample. Here is the persistent class with one lazy loading field:
[HierarchyRoot]
public class Country : Entity
{
[Field, Key]
public int Id { get; private set; }
[Field(Length = 30)]
public string Name { get; set; }
[Field(Length = 3)]
public string Code { get; set; }
[Field(LazyLoad = true)]
public string Description { get; set; }
public Country(Session session)
: base(session) {}
}
Say, we want to have a cache of countries in our application. We create some countries on Domain start, e.g.:var domainConfiguration = DomainConfiguration.Load("Default");
var domain = Domain.Build(domainConfiguration);
using (var session = domain.OpenSession())
using (var tx = session.OpenTransaction()) {
new Country(session) {
Code = "AND",
Name = "Andorra",
Description = "A tiny country in the middle of Europe"
};
new Country(session) {
Code = "ATA",
Name = "Antarctica",
Description = "Icy paradise for penguins"
};
// other countries...
tx.Complete();
}
To implement some sort of cache in earlier version of DataObjects.Net you would load countries in every transaction or avoid frequent loading of persistent objects from database by converting them into some kind of POCO and cache them.
In DataObjects.Net 5.0 you can do this in a more comfortable way using the new NonTransactionalReads flag.
// Configuring session
var options = new SessionConfiguration(SessionOptions.Default | SessionOptions.NonTransactionalReads);
var session = domain.OpenSession(options);
Dictionary<string, Country> cache;
// Loading cache with data in one transaction
using (var tx = session.OpenTransaction()) {
cache = session.Query.All<Country>().ToDictionary(i => i.Code);
tx.Complete();
}
// accessing data from another transaction
using (var tx2 = session.OpenTransaction()) {
// cached objects are not being reloaded from database. they are consumed as is
var antarctica = cache["ATA"];
Console.WriteLine(antarctica.Name);
// accessing a lazy loading field. session loads it on demand
Console.WriteLine(antarctica.Description);
tx2.Complete();
}
// disposing session. Data is not accessible anymore
session.Dispose();
What is more interesting, the same behavior can be achieved without using any transactions at all. Let's re-write the sample:
// Configuring session var options = new SessionConfiguration(SessionOptions.Default | SessionOptions.NonTransactionalReads); var session = domain.OpenSession(options); Dictionary<string, Country> cache; // Loading cache with data without any transaction cache = session.Query.All<Country>().ToDictionary(i => i.Code); // accessing data var antarctica = cache["ATA"]; Console.WriteLine(antarctica.Name); // accessing a lazy loading field. session loads it on demand Console.WriteLine(antarctica.Description); // disposing session. Data is not accessible anymore session.Dispose();
So, the key points of the NonTransactionalReads mode:
- No matter how data is loaded from database (with the help of transaction or not), it is accessible from outside the boundaries of the transaction, if any.
- Data is cached on Session level. As long as the Session is alive (not disposed), the data will be available from its cache.
- In case of accessing LazyLoad fields, Entity references and EntitySets, data is automatically fetched from database on demand.
