Re: UML class diagram -> SQL-DBMS tables
Date: Thu, 9 Oct 2003 08:50:08 +0200
Message-Id: <20031009085008.28fc0628.wettin_at_users.sourceforge.net>
On 8 Oct 2003 06:00:14 -0700
rgaffuri_at_cox.net (Ryan Gaffuri) wrote:
> karl wettin <wettin_at_users.sourceforge.net> wrote in message
> news:<20031006025702.353c70ec.wettin_at_users.sourceforge.net>...
> > Group,
> >
> > I'd like to hear your opinions on my way of representing an UML
> > class diagram as SQL-DBMS tables.
> www.odtug.org
>
> There is an article in a recent journal about using object views as a
> layer on top of your relational database that maps to classes. Its
> oracle specific, but Id assume that other vendors have similiar
> implementations.
I suppose you mean odtug.com? It sounds really interesting, but the $125 fee is a bit too much for one article.
> I do NOT like the idea of mapping classes to tables. Makes the
> relational model too complex. A middle layer is better.
I'm up for that, but exactly what would that middle layer do?
Basically, I'm trying to simulate an OODBMS in an SQL-DBMS.
> one thing to be careful of. Most vendors are using CBOs now and
> heavily 'layered' views tend to have performance issues in a CBO
> environment.
> If you go 5-7 layers deep with views and make them complex. So mapping
> needs to be cautious and dont over do it.
I've been trying to find information abount Common Business Objectss, but can't seem to find anything concrete. Could you please give me a small abstract description?
karl
-- http://sf.net/projects/silvertejp/ [abstract Human]<|--+--[Woman]<>-- +mother +child {0..*} --[Human] \--[Man]<>-- +father +child {0..*} --[Human] "arghhh .. it's all in geek" - objectmonkey.comReceived on Thu Oct 09 2003 - 08:50:08 CEST