IList support in Code-Only scenarios - Telerik Data Access now supports IList Fluent Mapping for IList properties based on primitive types.
Improvements for Sequence Columns mapping in Code-Only scenarios - Improvements are implemented in the Fluent API Sequence Column mapping for IList, Array and join tables. Now those mappings can be used in a backend independent manner, without specifying SQL types, only providing general guidelines about the type requirements (length, scale, "max" size, etc).
Oracle: Constraints from tables to views were not detected - Constraints that were pointing from a table to a view in an Oracle database were not shown in the Visual Designer. Currently Telerik Data Access is able to correctly detect such cases.
Telerik OpenAccess ORM renamed to Telerik Data Access
Re-branding: Colors and logos are now changed to match the new Telerik branding
BREAKING CHANGE: Mapping Sequence columns in Fluent API
OpenAccess NuGet packages renamed - The NuGet packages OpenAccess.CodeOnly, OpenAccess.CodeOnly.Sample and OpenAccess.Core are now deprecated. A new set of NuGets is provided instead - Telerik.DataAccess.Fluent, Telerik.DataAccess.Fluent.Sample, and Telerik.DataAccess.Core.
Visual Studio 2008 not supported anymore - Visual Studio 2008 will not be supported anymore by Telerik Data Access. You are invited to use the contemporary versions 2010, 2012 or 2013. For more information, see this blog post.
Oracle 9i not supported anymore - Oracle 9i is not tested anymore with Telerik Data Access. We strongly advise you to migrate to the contemporary versions 10, 11 or 12. For more information, see this blog post.
"Classic" Wizards not supported anymore - The "OpenAccess Classic" wizards will not be supported anymore. We strongly advise you to migrate to the new mapping approaches of Telerik Data Access - Visual Designer or Code-Only (Fluent) Mapping. For more information, see this blog post.
MySQL 5.0 not supported anymore - Telerik Data Access is not tested anymore against the legacy 5.0 version of MySQL. We strongly advise you to migrate to the more contemporary versions of MySQL. For more information, see this blog post.