DomainModel vs. Reverse Mapping

Thread is closed for posting
3 posts, 0 answers
  1. Stuart Miller
    Stuart Miller avatar
    7 posts
    Member since:
    May 2010

    Posted 09 Jun 2010 Link to this post

    I'm evaluating OpenAccess ORM for an enterprise level application and I'm in need of some advice.  I'm using VS 2010 and had started learning by using Reverse Mapping to generate my database objects.  I noticed that you have just added support in VS 2010 for the Domain Model visual designer, and it looks to be very customizable.  Now I'm trying to decide if this is how I should design the Model of my project.  Am I right in assuming that the two are mutually exclusive?  It appears that if one chooses to add a Domain Model object to the project, you can't use persistent classes, is this correct?  Which is the preferred method?  Which is more powerful?

    Thanks for the Help,

  2. Steve
    Steve avatar
    1888 posts
    Member since:
    Dec 2008

    Posted 09 Jun 2010 Link to this post

    Domain Model essentially is Reverse mapping right now, just the new way of doing it.  From what I understand they want to move us all off the older RevMapping wizard.

    I haven't had a chance to use it yet, but the scopeless functionality makes me think it's far superior
  3. Dimitar Kapitanov
    Dimitar Kapitanov avatar
    632 posts

    Posted 10 Jun 2010 Link to this post

    Hi Guys,
    So straight to the questions:

    1. Yes our intention is to remove the classic (wizard based) approach for Reverse/Forward mapping and mold them into a single round-tripping designer (version 1 is the currently available one for reverse mapping). We hope we can do so for Q2 2010.

    2. Actually this approach is a lot more powerful that the old one - not only visually and as interaction, but also you don't have two artificial workflow (reverse/forward) scenarios, but instead you will be able to intelligently manage the differences between model and schema in the data store in an seamless way. All that comes with Q2 and beyond.

    3.Currently the Visual Designer is aimed at the basic scenarios. It does not support some really neat parts of OpenAccess as the optimizations (Fetch Plans) and some database specific settings - currently they are available only through the old UI and API.

    Based on that, my advice is:

    1. If you have to start developing an enterprise application right away, you should use the old way of doing things. Later on we will assist you into porting to the new API/Designer, plus we will release an upgrade tool for OpenAccess in Q2 (of course it will not be able to magically translate the application without any problems but it will help a lot).

    2. If you don't have the intention to start immediately developing high-end features in an Enterprise application, I suggest you take a look at the Visual Designer, and if the time-frame for Q2/Q2 SP1 (mid/late July) is acceptable for you (we will have there round-tripping designer that allows forward mapping as well, new Fetch plans API, Backend Settings (store specific) functionality, very good Ria Services integration, etc.) maybe you should start form the beginning using the new approach provided by the product. Don't hesitate to ask any questions you might have.


    Kind regards,
    Dimitar Kapitanov
    the Telerik team

    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
Back to Top