This NuGet Package is deprecated since the product has been renamed to Telerik Data Access. Please use Telerik.DataAccess.Core instead.
- Support of ICollection<T>.Contains(T) and Enumerable.Contains<T>(IEnumerable<T>,T) in LINQ projection - ICollection<T>.Contains(T) and Enumerable.Contains<T>(IEnumerable<T>,T) are now supported in the LINQ projection expressions, so that they become usable in group aggregate expressions.
- The old OpenAccess ORM packages are deprecated and are not updated any more - The old OpenAccess.* NuGet packages not be uploaded any more. All projects using them should be migrated to their corresponding Telerik.DataAccess.* packages:
OpenAccess.Core -> Telerik.DataAccess.Core
OpenAccess.CodeFirst - > Telerik.DataAccess.Fluent
OpenAccess.CodeFirst.Sample -> Telerik.DataAccess.Fluent.Sample
With this last release of the old OpenAccess.* packages, they are made dependent on the latest Telerik.DataAccess.* packages without specifying a version.
- NullReferenceException when second level cache cluster is used in a setup with clients using different meta data and an object with internal identity is evicted - Now the distributed L2 cache is functioning properly when participating servers have similar, but not identical metadata.
- Attempting to read unsigned value stored in some backends resulting in a System.OverflowException - Reading unsigned numeric columns (like ushort) will no longer cause System.OverflowException when loading data from a database supporting unsigned types.
- When calling GetMemberNames() on entity type with internal version column, voa_version member unexpectedly returned - GetMemberNames() method in the OpenAccessContext is no longer returning internal version column (voa_version) for types using ConcurrencyControl.Version.
- OpenAccessContext.GetMemberNames() not returning members defined in base types - OpenAccessContext GetMemberNames() API now returns members defined in base type(s) of the current type.
- Schema Migration: Exception caused by index creation for VARCHAR(MAX) columns - Telerik Data Access will no longer try to automatically create database indexes over data types that cannot be indexed (e.g. varchar(MAX), nvarchar(MAX), blob and etc.) when creating or migrating database schema.
NOTE: These Release Notes include only the runtime changes in the particular Telerik Data Access release. For the full list of changes please refer to the Telerik web site ( http://www.telerik.com/support/whats-new/data-access/release-history ).