Thank you for pointing that out, we will consider adding an option to completely exclude a table (or any other relational object) from the model.
We have already addressed the issue of loading all Oracle schemas. With the next version of the product (even in the internal build which should be available in a few days) you will be able to select from a list which schemas are read and shown in the treeview of the Add new item wizard.
7) In the join table combobox we are currently showing only the tables which are detected as join tables and the ones created by the "Create new join table" option. So if your table has more than two foreign key columns, most likely it will not be shown in the dropdown. In one of the next versions we will provide an option to manually set if a table is actually a join table.
8) This seems to be related to the problem you described in the last two posts. We are still investigating this behavior and will let you know when we have more information. We are sorry for the troubles you are experiencing with our product, we will do our best to solve them soon.
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?
Telerik Public Issue Tracking
system and vote to affect the priority of the items