Database Modeling - Logical and Physical

[edwar64896]

Am currently evaluating EA, so pls forgive newbie questions...

1. Previously used a database modelling tool that allowed the creation of a "logical' schema diagram" that would then autmoatically create a "physical" diagram containing all FK relationships and intermediate tables (for N:N joins) where necessary. Can EA do this, or do I have to manually create all FK relationships and intermediate tables?

2. Want to be able to create get_ and set_ methods for class entities automatically...

3. WAnt to be able to create persistence code for a database schema I am designing. At the moment, I don't seem to be able to create any code based on any "Table" stereotypes. EA tries to create the files, but they are all empty! Must be doing something wrong here... I'm lazy and just need a quick way of dumping out a persistence interface.

Tkx
Mark

[thomaskilian]

Sorry, I'm no data modeller, but I'll try to give some hints:

1. Previously used a database modelling tool that allowed the creation of a "logical' schema diagram" that would then autmoatically create a "physical" diagram containing all FK relationships and intermediate tables (for N:N joins) where necessary. Can EA do this, or do I have to manually create all FK relationships and intermediate tables?

EA can assist you in doing that. You can transform a logical model (context menu Transform Current Package in Project View) into tables and maintain foreign keys (context menu for associations between tables). The help is fine so you can reproduce the steps.

2. Want to be able to create get_ and set_ methods for class entities automatically...
 
3. WAnt to be able to create persistence code for a database schema I am designing. At the moment, I don't seem to be able to create any code based on any "Table" stereotypes. EA tries to create the files, but they are all empty! Must be doing something wrong here... I'm lazy and just need a quick way of dumping out a persistence interface.

For that you need according classes which you can create from you logical model with another transformation (to e.g. C# or whatever). These classes can be augmented with get/set for the attributes (open their properties).

In the end you have a logical model from which you create tables and classes for persistence.