Productivity

Telerik OpenAccess ORM let you work your preferred way: either you start with your object model and Telerik OpenAccess ORM generates/maintains your database schema for you, or just start with your existing schema and let Telerik OpenAccess ORM reverse map it to a new object model.   Telerik OpenAccess ORM provides support for both approaches for years and it will get even better by providing complex functionalities out of the box like Roundtrip Mapping (see below). Because we are getting requests for ‘Model First’ functionalities by our customers, and this is the way the upcoming version of Entity Framework names the Forward mapping...

Unit testing the DAL has always resulted in a debate: whether to mock or not the Data Access Layer. Indeed, there are cases were the DAL cannot be legally tested without hitting the real production database (requires integration testing). The goal behind that is to assure us of the behavior of some database server specific features like primary key generation, handling schema alternations with pre-populated data, triggers, etc.. However for testing the Business Logic Layer , the validation logic or the presentation layer, it is fair to say that accessing the database is...

Telerik OpenAccess ORM generates dynamic SQL to perform CRUD operations. If for some reason you are not comfortable using dynamically generated SQL or your company policies allow data manipulation only via stored procedures, fear not. Telerik OpenAccess ORM supports CRUD operations via stored procedures too – currently only for MS Sql Server, but soon for the other backends also.  Stored procedure usage in Telerik OpenAccess ORM can be classified into 2 categories – Mapping existing stored procedures and instructing Telerik OpenAccess ORM to use them instead of generating dynamic SQL Letting Telerik OpenAccess ORM generate and use the required stored procedures based...

We all know that today LINQ is the most popular and easy way for processing data in the .NET community. In fact you can use almost all data sources you might think of: plain objects, XML or relational databases. While we have been offering an extensive LINQ support for months now, and we are continuously improving it, I don’t think it received the credit it deserves. So we decided to foster the awareness of our community towards the great LINQ support we provide with the Telerik OpenAccess ORM tool. Ok, easier said than done. What approach should we take with this one? A...

What usually is of great importance to developers that use ORM tools, are issues related to concurrent updates or deletes that can potentially cause a valuable loss of data, and how the ORM framework handles the cases. Because of the state-less nature of HTTP the object-scope is re-initialized on every postback. That is an operation on its own, future blog-posts will cover some of the best practices approaches to object scope life-cycle management. The problem with stateless scenarios is that all change-tracking that the object-scope does for us in a desktop scenario is lost on every postback so there is a...