Re: The wisdom of the object mentors (Was: Searching OO Associations with RDBMS Persistence Models)
From: Robert Martin <unclebob_at_objectmentor.com>
Date: Wed, 28 Jun 2006 08:44:21 -0700
Message-ID: <2006062808442182327-unclebob_at_objectmentorcom>
> benefit
>
>
>
>
> True, but it does need to know if you use relational model or something
> else.
Date: Wed, 28 Jun 2006 08:44:21 -0700
Message-ID: <2006062808442182327-unclebob_at_objectmentorcom>
On 2006-06-20 23:51:04 -0700, "x" <x_at_not-exists.org> said:
>
> "Robert Martin" <unclebob_at_objectmentor.com> wrote in message
> news:2006062013130599097-unclebob_at_objectmentorcom...
>> On 2006-06-13 08:30:53 -0400, "x" <x_at_not-exists.org> said: >> >>> You can isolate SQL and its functionality in a module, but the interface >>> will still be dependent of the functionality of SQL if you want to
> benefit
>>> from it, I guess.
>
>> True, but the interface will only depend on the abstract nature of the >> SQL functionality. Thus:
>
>> Employee* getEmployee(int empId);
>
>> I can certainly implement this with SQL, but I could implement it any >> of a number of different ways too. The caller does not need to know >> that I am using SQL.
>
> True, but it does need to know if you use relational model or something
> else.
Why? Getting an employee is getting an employee. Whether the mechanisms employs a relational engine or not.
-- Robert C. Martin (Uncle Bob) | email: unclebob_at_objectmentor.com Object Mentor Inc. | blog: www.butunclebob.com The Agile Transition Experts | web: www.objectmentor.com 800-338-6716 |Received on Wed Jun 28 2006 - 17:44:21 CEST