Re: Mixing OO and DB
Date: Fri, 15 Feb 2008 16:14:35 -0800 (PST)
Message-ID: <ab2c4c7d-e266-4d31-be39-c5db8c455553_at_s37g2000prg.googlegroups.com>
On Feb 12, 6:49 pm, Robert Martin <uncle..._at_objectmentor.com> wrote:
> On 2008-02-11 12:44:28 -0600, topmind <topm..._at_technologist.com> said:
>
> > A bigger issue is how to manage "variations on a theme". OOP tends to
> > use polymorphism and object pointers, while a data-centric approach
> > tends to use set theory and attributes (meta data). I much prefer the
> > second. I won't claim it objectively better, but to my mind it is a
> > lot nicer, more flexible, and easier to report/study/sift via query
> > and table browsers.
>
> I won't disagree with any of that. I will say, however, that I can
> manage the dependencies between source code modules with OO,
> and I can't with data.
The trick is to shift to a declarative interface/logic so that less
is
in app code. Change the problem instead of trying to solve the
wrong problem.
> There are other dependencies I can manage with data,
> that I can't with OO. Both are useful. Neither is better than the
> other. They are orthogonal and complementary.
I disagree. They tend to fight over the same territory.
>
> --
> Robert C. Martin (Uncle Bob) | email: uncle..._at_objectmentor.com
> Object Mentor Inc. | blog: www.butunclebob.com
> The Agile Transition Experts | web: www.objectmentor.com
> 800-338-6716 |
-T- Received on Sat Feb 16 2008 - 01:14:35 CET