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 scenarios, we would like to shed some light how it translates in the context of Telerik OpenAccess ORM:
- Entity Frameworks Model First equals Telerik OpenAccess ORM Forward Mapping
- Entity Frameworks Schema First equals Telerik OpenAccess ORM Reverse Mapping
This is featured on our product information page including further links to the relevant demos.
- Forward Mapping (model-first) - OpenAccess allows you to start working from scratch with your object model and just creates your new relational database with an optimized data schema. You dont need to think in relations anymore, but you still can. OpenAccess optionally allows you to define almost any kind of schema and you can influence the given names of tables or columns. See demo
- Reverse Mapping (schema-first) - OpenAccess additionally allows you to start with your legacy database. The reverse mapping experience begins the minute you connect your new Visual Studio project to the legacy database using the Reverse Mapping wizard. OpenAccess recognizes the data model, data types and additional information like keys and creates the matching object model. Then you can start designing and developing your new .NET application. See demo
So moving forward, we will start using both wordings simultaneously and transition to the Entity Framework wording to make life easier for you.
Furthermore we have already introduced:
- Roundtrip Mapping - You can even change directions: any change in the object model will change optionally your schema and any change in the database can optionally change your object model.
If you are totally new to ORM, Scott Amblers introduction to mapping might still be helpful.
To learn more about the various mapping techniques you can have a look to Object Relation Mapping Strategies and how to do it with OpenAccess in the documentation:
A good introduction into OpenAccess is the recorded Webinar (watch online, download wmv), which demonstrates Model First and Schema First, or the Falafel OpenAccess Made Easy courseware (available printed for purchase or free to download).
Further resources:
Model First / Forward Mapping
Schema First / Reverse Mapping
Entity Framework Model First Introductions: