• .NET

    Using user-defined methods in a LINQ query

    As you are aware, for a given LINQ query Telerik OpenAccess ORM tries to push the query parts to the server as far as possible. Doing so minimizes the amount of data fetched from the server. For example, consider this very simple query that fetches all discontinued Product entities from the Northwind database. var query = from p in scope.Extent<Product>()             where p.Discontinued             select p;   The generated SQL statement would similar to -...
    May 11, 2010
  • .NET

    Telerik OpenAccess ORM Concurrency Control

    Telerik OpenAccess ORM provides you with a mechanism to handle the Concurrency control. Concurrency control is the management of contention for data resources. It ensures that the transactions are executed following the ACID rules. There are two concurrency control schemes: pessimistic and optimistic. A concurrency control scheme is considered pessimistic when it locks a given resource early in the data-access transaction and does not release it until the transaction is closed. A concurrency control scheme is considered optimistic when locks are acquired and released over a very short period of time at the end of a transaction. The Telerik OpenAccess supports several modes for Concurrency...
    May 10, 2010
  • .NET

    Validating Your Domain Model

    With the Q1 Release of the Telerik OpenAccess ORM we introduced the new Visual Designer for OpenAccess. In a nutshell it’s a drag-and-drop editor that visualizes the mapped classes and their relationships. It is a great improvement and people are often stunned by it. One of the coolest features that it presents though is often overlooked. OpenAccess gives you the possibility of validating your model. Note that this is extremely helpful due to the fact that you are able to build your solution with an invalid model and then get errors in the runtime. On top of that it also suggests...
    April 26, 2010
  • .NET

    Looking at the Telerik OpenAccess ORM Visual Designer Toolbox

    The Telerik OpenAccess ORM Visual Designer provides toolbox items that one can use to update and fine tune the persistence model and how the entity classes will behave. Inheritance - like other objects, the mapped entity classes can be used in inheritance scenarios and can be derived from other classes. The Telerik OpenAccess ORM provides the power of inheritance to the data access layer. Classes in an inheritance hierarchy can be mapped to the same table (flat mapping) or to different tables (vertical mapping and horizontal mapping), or a combination of two strategies (mixed flat and vertical). The Telerik OpenAccess ORM Visual...
    April 24, 2010
  • .NET

    Telerik OpenAccess ORM and the XML Metadata Source

    We all know that Telerik OpenAccess ORM has a completely new face with the Q1 2010 release so it is about time to start blogging about some of the features and improvements that the new Visual Designer brought along.  Today I will talk about one of the most notable changes in the new version of OpenAccess ORM and that is the “XML – only” mapping. You all know that so far with the previous versions of the product the mapping information was defined by a mix of XML configuration files and CLR attributes. After a lot of customer feedback and...
    April 23, 2010