News, examples, tips, ideas and plans.
Thoughts around ORM, .NET and SQL databases.

Thursday, February 15, 2018

DataObjects.Net 5.0.17 Beta 3

We have released a new version of DataObjects.Net

In the version following changes were performed:

[main] Fixed certain scenarios when In() or Contains() operations in query led to  NullReferenceExecption exception
[main] Persist operation no longer breaks enumeration of EntitySet items.

Detailed explanation of these changes is in the post.

As usual you can get it from our website or install from Nuget library.


Tuesday, January 16, 2018

Winter sale


This year we're starting our winter sale right on January 16. Just use the coupon code DO2018 on checkout and get 50% off all editions of DataObjects.Net. If you want to renew your subscription use DO2018RENEWAL to get 70% discount. 

This special on our products is valid until Wednesday 31 January 2018.

Should you have any questions, please email to sales@dataobjects.net.

Monday, January 15, 2018

DataObjects.Net 5.0.17 Beta 1 and 5.0.17 Beta 2

We've released two beta releases recently and here are the featured changes

5.0.17 Beta 1:

[main] Decreased amount of metadata extracted while building Domain or Storage node in DomainUpgradeMode.Skip mode.

5.0.17 Beta 2 :

[main] Added sharing of storage schema across Storage nodes


You can read details of the changes inside. And as always you can install the releases from Nuget library or download from our website.


Friday, December 01, 2017

DataObjects.Net 5.0.16

We've released a new version recently. Here are the changes we have made:

[main] Fixed null reference exception which might appear on constraints validation

As usual you can download it from our official website or install it from Nuget library

Friday, October 06, 2017

DataObjects.Net 5.0.16 Beta 1

We've released a new version recently. Here are the changes we have made:

[main] Added constraint option allowing to skip the constraint if the field isn't changed
[main] DifferentialTuple.Merge() operation no longer causes StackOverflow exception
[main] Fixed certain cases of foreign key absence for reference fields of structures
[main] Fixed translation of enum value as default field value
[sqlserver] Fixed extraction of information about indexes from database

As usual you can download it from our official website or install it from Nuget library

Complete changes description is below.

Monday, June 19, 2017

DataObjects.Net 5.0.14

We've released a new final version recently. Here are the changes we have made:

[main] Returned expected behavior of delayed queries which was changed in 5.0.11 by bug fix for IN() operation.

In 5.0.11 we had made some changes and fixed certain cases of IN() operation usage which supposed to create temporary table, but didn't. These changes brought unexpected behavior for delayed queries. In this release we kept the cases fixed and returned old behavior for delayed queries.

[main] Fixed bug when Server profile sessions allowed to query database without transaction.

IMPORTANT! This bug fix might be a breaking change for those users who already use it. Officially, SessonOptions.ServerProfile option does not allow queries outside of transaction. So we have returned this behavior. If you require such non-transactional queries, you should include an additional option to your session configuration - SessionsOptions.NonTransactionalReads.

[mysql] Corrected column types' extraction.


As usual you can download it from our official website or install it from Nuget library

Tuesday, January 31, 2017

DataObjects.Net 5.0.11

We've released a new final version recently.

We performed following changes:

[main] Constraints can be skipped on transaction commit
[main] Operations like EntitySet<T>.ToList() no longer lead to incorrect EntitySet<T>.Count value
[main] IN() operation now creates temporary tables when it supposes to
[main] Fixed translations of aggregates like IQueryable<T>.Sum() when selector parameter can be omitted
[main] Enum constants in IndexAttribute.Filter expression are translated correctly now
[main] Fixed certain scenarios when enum constants caused query translation error



As usual you can download it from our official website or install it from Nuget library

Monday, December 26, 2016

Winter sale



This year we're starting our winter sale right on December 27. Just use the coupon code DO2017 on checkout and get 50% off all editions of DataObjects.Net. If you want to renew your subscription use DO2017RENEWAL to get 70% discount. 

This special on our products is valid until Wednesday 15 January 2017.

Should you have any questions, please email to sales@x-tensive.com.

Friday, December 23, 2016

DataObjects.Net 5.0.11 RC2

We released DataObjects.Net 5.0.11 RC2 last Friday. The list of changes is below:

[main] Fixed build in Perform/PerformSafely modes when there is no Metadata tables in database/schema
[main] Added support for CONTAINSTABLE queries for SQL Server providers
[main] Optimized memory usage for storage nodes which are build in Skip mode
[main] Full-text indexes are now allowed for fields of structures
[main] Added highest ranked matches limitation support for free-text queries
[main] ReferenceFinder now excludes references which were locally removed
[main] Fixes certains scenarios when changes do not clear on after persist
[postgresql] Fixed extraction of columns associated with DateTimeOffset fields


As usual you can download it from our official website or install it from Nuget library

Thursday, September 22, 2016

Support for DateTimeOffset for PostgreSQL provider


We have introduced DateTimeOffset support for PostgreSQL provider in 5.0.11 RC. Here, we want to explain some restrictions of this RDBMS which affect our implementation of that type support.

We warn you that support for date/time with time zone is different from Oracle Database and Microsoft SQL Server implementations. The last two RDBMS has full support for all parts of date/time including time zone, but PostgreSQL doesn't.

If you want to use DateTimeOffset type in domain models on PostgreSQL storage we need to explain some things you may face with.