Re: Mixing OO and DB

From: Bob Badour <bbadour_at_pei.sympatico.ca>
Date: Wed, 20 Feb 2008 12:36:16 -0400
Message-ID: <47bc5706$0$4048$9a566e8b_at_news.aliant.net>


topmind wrote:

> On Feb 20, 6:03 am, Robert Martin <uncle..._at_objectmentor.com> wrote:
> 

>>On 2008-02-19 12:40:27 -0600, topmind <topm..._at_technologist.com> said:
>>
>>
>>>>Yet even in the most data driven application there will still be
>>>>behavior, and there will be code that implements that behavior, and
>>>>there will be dependencies between the elements of the source code that
>>>>need to be managed.
>>
>>>Yes, but behavior tends to be "neutered" in data-driven apps such that
>>>OO's change-handling techniques are less useful there.
>>
>><<quasi-political metaphor elided>>
>>
>>That's not the point. The point is that wherever there is code there
>>are dependencies that need to be managed, and OO is a useful tool that
>>helps with that management.

Martin is talking out of his ass again. Sure, dealing with dependencies is a major focus when one writes code in OOPLs because OOPLs actually make that far more difficult. As soon as one hides the implentation of a class, one hides the dependencies.

Contrast that with any dbms where one can find the dependencies quickly just by examining the system catalog. Hell, even SAP's ABAP, which is as far from OO and as far from modern as one can imagine, has a handy little "where used" icon that will spit out dependencies in a heartbeat.

Martin is a self-aggrandizing ignorant moron. Received on Wed Feb 20 2008 - 17:36:16 CET

Original text of this message