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

From: David Cressey <dcressey_at_verizon.net>
Date: Wed, 31 May 2006 18:14:41 GMT
Message-ID: <l2lfg.44$Eo3.7_at_trndny02>


"Robert Martin" <unclebob_at_objectmentor.com> wrote in message news:2006053108292037709-unclebob_at_objectmentorcom...
> On 2006-05-30 06:31:53 -0500, "Erwin" <e.smout_at_myonline.be> said:
>
> > Little point in preaching to the chuiar of course (how do you spell
> > that damn word ?).
> >
> > Go tell this on an Otherwise Oriented forum, you'll get dawnbashed.
> >
> > That said, application code is still highly important because it's
> > needed to fill all the holes that current dbms's still leave wide open
> > in the area of constraint enforcement.
>
> This statement is fascinating. It takes the view that the majority of
> the system is DB and that application code simply fills the cracks.
> The DB represents the bricks and the application code is the mortar.
>

I think the validity of your point of view depends on whether you view the database as belonging to a single application, or whether multiple applications, perhaps originally provided by different vendors, collaborate with each other by using the same database to store persistent data.

Most people who have worked in application development workshops assure me that such a scenario is unheard of. on the other hand, I assure you that, when the ideas about enterprise databases were being developed in the 1960s and 1970s, this was at the heart of what a database was all about. The idea of embedding a "data bank" (if you prefer that terminology) in a single application would have struck them as quaint, bordering on absurd.

>
Received on Wed May 31 2006 - 20:14:41 CEST

Original text of this message