Re: Mixing OO and DB
Date: Thu, 6 Mar 2008 02:03:02 -0600
On 2008-03-04 17:06:57 -0600, topmind <topmind_at_technologist.com> said:
>> What you are missing is that there is
>> no restriction that other objects use the data from the employee_table.
>> So while a class certainly defines the methods that can be used to
>> access and manipulate the data within that class, there can be many
>> different classes that use the same data in very different ways.
> In other words, each class becomes a little roll-your-own database
> with a very custom interface.
Each small group of classes becomes a little roll-your-own data access and manipulation scheme that is perfectly tuned for it's very specific purpose.
Granted. Very useful.
> OO does
> not, making it primitive and tedious.
Stupid sloganeering with no substance behind it.
That sentence is true. It is also true if you replace the phrase "the
> one learns to leverage those idioms provided by the DB, then the code
> is simpler because it doesn't have to reinvent them.
That sentence is true. It is also true if you replace the phrase "theDB" with the word OO.
-- 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 Thu Mar 06 2008 - 09:03:02 CET