Database Modelling in UML

The Methods & Tools newsletter has released in its archive section the
article "Database Modelling in UML". This article offers a step by step
approach to transform a UML object-oriented class model in a purely
relational database.

http://www.methodsandtools.com/archive/archive.php?id=9Franco Martinig via SQLMonster.com wrote:

> The Methods & Tools newsletter has released in its archive section the
> article "Database Modelling in UML". This article offers a step by step
> approach to transform a UML object-oriented class model in a purely
> relational database.
> http://www.methodsandtools.com/archive/archive.php?id=9

The article is rather difficult to believe after lines like this:

"The relational model only offers a public data access model. All data is
equally exposed and open to any process to update, query or manipulate it.
Information hiding is unknown."

This statement is true in the same sense that it is true that you have to
turn a crank on the front of a car to get it started. It depends on
whether or not you are Rip Van Winkle.

I kept reading looking for a qualifier, but the mistake is repeated later
on, "The relational model exposes all data equally, with limited support
for associating behaviour with data elements through triggers, indexes and
constraints."

--
Kenneth Downs
Secure Data Software, Inc.
(Ken)nneth@.(Sec)ure(Dat)a(.com)|||Perhaps for another perspective, read:
http://www.dbdebunk.com/page/page/622916.htm
http://www.dbdebunk.com/page/page/622867.htm

--
Anith