Best practice for creating a entity that is a subset of another

Thread is closed for posting
2 posts, 0 answers
  1. Jack
    Jack avatar
    45 posts
    Member since:
    Feb 2009

    Posted 25 Mar 2011 Link to this post

    I have an extract_job table which is the header table for a job to extract data.  The table contains a few dozen columns of which most are processing and post extract information.  When I create the job I only need a few basic columns to send to the UI and for another use case where the user can choose to re-run a job I again only need a few of the columns.

    If I was starting from the Oracle DB I would create the base table, and three views (full, new, re_run).

    How do I start this from the modelling side?  Is it a partial inheritance?  How do I tell OpenAccess that I want a view?


  2. Zoran
    Zoran avatar
    534 posts

    Posted 31 Mar 2011 Link to this post

    Hi Jack,

     It is not possible to create a view from the designer if you do not have it in the database. The workflow is to create a view in your database and then map it on the designer surface. For example, if you have your model already created, you can use the Update From Database wizard in order to update your domain model with the view you have created in your database.

    the Telerik team
Back to Top