Re: The wisdom of the object mentors (Was: Searching OO Associations with RDBMS Persistence Models)

From: Marshall <marshall.spight_at_gmail.com>
Date: 4 Jun 2006 16:44:21 -0700
Message-ID: <1149464660.970160.219170@u72g2000cwu.googlegroups.com>

Sasa wrote:
> mAsterdam wrote:
> >
> > And all tables, columns and constraints in your schema
> > were designed and named by the object-persistence layer
> > designers/programmers, for programs.
> > ...
>
> No. They should be designed semi-independently of the object persistence
> layer. The client (app(s)) dictates what it wants. The DBMS chooses how
> will it present it. The mapper, simply translates.

Why would you do that? The requirements dictate the conceptual model. The conceptual model dictates the logical model. The logical model is the database schema. The conceptual model also dictates what the application code needs to do.

If you have done the above correctly, there is no "separation" between the schematic needs of the database and those of the application. There is certainly no need for "independence."

Marshall Received on Sun Jun 04 2006 - 18:44:21 CDT