Take the 2-minute tour ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

I used to make database designs using a french method called MERIS that uses mainly two diagrams to create the database (MCD and MLD), then i heard about UML and that is used also for databases and not only for coding, i thought it has some special diagram for database design, but i noticed that some people use class diagram to make a database design, i find it not compatible with this because :

  • it uses many concepts that doesn't exist on RDBMS (inheritance, methods, aggregation, composition, methods, access modifiers)
  • UML is a modeling language and not a methodology so it doesn't specify rules how to pass from the diagram to the relation Schema.

Question is : Is UML a nice choice for a database design ?

share|improve this question
    
I agree. A search on "erd vs uml" gives some interesting results though. –  Louis Somers Mar 2 '13 at 16:32
1  
inheritance definitely exists in RDBMS –  Neil McGuigan Mar 2 '13 at 18:37
    
@NeilMcGuigan: no it doesn't –  user2080105 Mar 3 '13 at 13:04
    
@user2080105 Totally, man. There is absolutely no inheritance in Postgres (postgresql.org/docs/9.1/static/tutorial-inheritance.html), and certainly no important figures in computer science have created patterns for it (martinfowler.com/eaaCatalog/singleTableInheritance.html) –  Neil McGuigan Mar 3 '13 at 17:48
    

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.