This is a migrated thread and some comments may be shown as answers.

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

1 Answer 86 Views
Getting Started
This is a migrated thread and some comments may be shown as answers.
This question is locked. New answers and comments are not allowed.
Jack
Top achievements
Rank 1
Jack asked on 25 Mar 2011, 06:52 PM
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?

Thanks

jack

1 Answer, 1 is accepted

Sort by
0
Zoran
Telerik team
answered on 31 Mar 2011, 08:12 AM
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.

Greetings,
Zoran
the Telerik team
Tags
Getting Started
Asked by
Jack
Top achievements
Rank 1
Answers by
Zoran
Telerik team
Share this question
or