5 Answers, 1 is accepted
OpenAccess provides you with a tool (Visual Designer) that separates the conceptual model from the relational model. In the Visual Designer you see/add/edit/delete the entities of the conceptual model while the actual tables to which the classes are mapped can be reviewed in the Model Schema Explorer.
In order to permanently remove a table from the domain model, you have to delete its class from the diagram displayed in the Visual Designer and the table itself from the schema shown in the Model Schema Explorer (You can start the Model Schema Explorer from View > Other Windows > Model Schema Explorer). There you have to expand the Tables tree, find the table you want to remove, right-click on it and select Remove table. OpenAccess will warn you that you are about to remove the constraints linked to the table too and if you click Yes, the table will be deleted.
In case you have accidently deleted the class from the diagram and you want it back, all you have to do is find the table in the Model Schema Explorer and drag-and-drop it in the Visual Designer (you do not need to update from the database).
The table will show in the Select Changes dialogue of the Update From Database wizard only if it was permanently removed / never added prior to the update.
Do not hesitate to get back to us if you have any other questions.
Greetings,
Doroteya
the Telerik team
I found another issue. If I have two tables in DB and create a Domain Module to select one table with uncheck "Generate Context Class" and "Mutipule File" option, it will create one entity class. Then If I right click the designer and choose "Update from Database" to select another table, it will not auto generate another entity class unless I enter "CLR +S" to save it. Whether have a way to generate the class after choose a table and click ok button instead of "CLR+S" because not all developer will always to save it after the action.
I understand your concern.
The reason behind this behavior is that this way we make sure the entire heavy process of code generation and processing of the changes is done only when the user explicitly starts it. If we apply the changes every time you do something on the designer surface, it would be a very unpleasant experience in case your model is larger. For the time being we are not planning to change that particular feature.
As we are currently working on improving the general experience with our Visual Designer, do not hesitate to get back to us with any other suggestions that can make your life easier when defining your model.
Ivailo
the Telerik team
Yes, you are absolutely correct. We will plan to better explain this requirement in the documentation and other resources we are offering.
Thank you for your feedback.
Ivailo
the Telerik team