Re: OO and relation "impedance mismatch"

"Kenneth Downs" <firstinit.lastname_at_lastnameplusfam.net> wrote in message news:fac1kc.83b.ln_at_mercury.downsfam.net...

> Here is an example of how different they are. Question: if you were
> designing a dd, and had complete freedom to do it anyway you wanted, how
> would you specify a foreign key? Well, we always start with the absolute
> simplest way and then embellish, so we get:

Well, if I had complete freedom, I'd substitute one of those fancy data modeling tools like Erwin or Data Architect for the DD, to begin with.

DA already maintains three different kinds of models, a Conceptual Data Model, a Physical Data Model, and an OO Case Model. Starting from any of them, you can derive the other two.

Then I'd add whatever features necessary to automate the trigger generation you were talking about, together with suppressing the inclusion of the IR constraints in the DDL. That way I could have my cake and eat it too. The biz rules, including Integrity rules, would be in "one master place", but I could choose which of them got enforced in the DBMS.

Next, I'd add support for some network and hierarchical DBMS products. Maybe throw in the Nelson-Pick model to see if it's as great as it's touted by the Pickies in here. Received on Wed Oct 06 2004 - 15:40:08 CDT