[Solved] Why I need to manual create tables for my entities in model-first approach?

[Stanislaw]

I'm starting a new project via model-first approach.
I was created about 10 entities with relations, and have next questions:

1. Is designer have a capability to create relational model automatically? If no - I can't see the increasing of my productivity when working with your product, because the generation of relational model is very logical feature.
2. How I can define a custom type in designer?
3. How I can define a fetch groups is designer?
4. How I can define the indexes in designer?

I have not found this.
Thank you.

[Stanislaw]

Up

[PetarP]

Hello Stanislaw,

 1. Yes the designer is capable of forward mapping your model. I believe that you will find the following help article useful.
2. Can you please specify what do you mean with a custom type?
3. Currently there is no design time support for fetchplans. However you can always define them during runtime using the approach described in this article.
4. Unfortunately indexes are not yet supported and I am afraid I cannot provide you with a workaround for this.
I hope that my answer were useful to you.

Best wishes,
Petar
the Telerik team

[Stanislaw]

Thanks for the answer!
1. I knew about capabilites of forward mapping, I was mean that for each created entity in designer I must manually define the table and columns in designer (not in database). Whay designer can not transform automatically my entities into tables?
2. Sorry for ambiguous - custom type = value type (embedded type)
3. Ok, but in old style of your designer tools I can to define the fetch plans (groups) - why this was removed?
4. Same as p.3

[PetarP]

Hi Stanislaw,

1. It can. If you run the wizard for classes that are not associated with any table our VSchema tool will create the required tables for you. Note that they will be created on your database server and you will need to merge them with your model manually using the Update From Database wizard. Please note that  we plan to automate the process in the future.
2. Such feature is not yet supported.
3 and 4. The features were not removed. They just need to have an equal representation in the Visual designer as  they had in the old reverse mapping wizard. This is scheduled for implementation and you will find it in one of our next builds.

Regards,
Petar
the Telerik team