Most of the time your class models are for the domain and business concepts and may vary dramatically with the needs of the database. Often times they match well with a logical ER model, but not always with the physical ER model.
Physical ER models deal with things such as constraints, alternate keys, foreign keys, partitions, etc. Things that are in the domain (class) models but not necessarily expressed. In a nut shell, they are both modeling the same business domain and needs. They just do it in different, but important, ways. On Fri, Mar 12, 2010 at 12:19 PM, CassioT <[email protected]> wrote: > Hi. > > I would like to know if you use Class Diagram, ERD's or none. I'm > asking because I already seem Fabio saying many times that he designs > the classes and generate the tables based on that and the mapping. He > can answer that, but if you do something like that, why should you do > an ERD? Just for doc? Maybe only a class diagram would be enough. > > I think that we will find all kind of combinations. ERD + CD, CD, ERD > and None > > Opinions? > > Cassio > > -- > You received this message because you are subscribed to the Google Groups > "nhusers" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<nhusers%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/nhusers?hl=en. > > -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
