Re: The wisdom of the object mentors (Was: Searching OO Associations with RDBMS Persistence Models)
From: Robert Martin <unclebob_at_objectmentor.com>
Date: Tue, 20 Jun 2006 15:18:21 -0400
Message-ID: <2006062015182140194-unclebob_at_objectmentorcom>
Date: Tue, 20 Jun 2006 15:18:21 -0400
Message-ID: <2006062015182140194-unclebob_at_objectmentorcom>
On 2006-06-02 08:28:55 -0400, "Tony Andrews" <andrewst_at_onetel.com> said:
>>
>> Yes, it would be a shame if we were unable to utilize the power of the
>> tool. So, what if we put the decoupling level a bit higher than the
>> schema. What if the application defines a set of data management
>> services that are implemented by another layer? What if that layer can
>> make use of all the nifty features of the DBMS? What if that layer
>> could also be replaced with a completely different mechanism?
> > What sort of things would this layer do? In my world it would perform > business logic, with procedures for actions such as "create employee", > "calculate payroll". However I suspect in yours these would be > DBMS-agnostic OO methods, and this layer would be doing something lower > level - though I can't quite imagine what other than generic "insert > [row] into [table]" type commands.
Create Customer (and all the other CRUD and etc functions) would be split between the two layers. Application management happens in the higher layer. Data access and management happens in the lower layer.
-- 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 Tue Jun 20 2006 - 21:18:21 CEST