Re: Mixing OO and DB

From: topmind <>
Date: Thu, 6 Mar 2008 13:23:41 -0800 (PST)
Message-ID: <>

Robert Martin wrote:
> On 2008-03-05 00:20:57 -0600, frebe <> said:
> > The reason OO people like to "decouple" the SQL statements is:
> > 1. OO languages doesn't have good support for embedding SQL.
> > 2. OO like to model data as a network graph, in opposite to the
> > relational model.
> OO people like to decouple SQL because
> 1. They don't like mixing high level policy code with low level detail
> code. They'd rather partition their code based on abstraction level.

You repeat the same simplistic slogans over and over again until you believe them, like Bush. SQL is *not* any more "low level" than your app language (unless you are using it wrong).

> 2. They don't like tying themselves to a particular implementation.
> They want to be able to easily replace the SQL with something else

Can you then hide OOP for me so that I don't have to deal with it? After all, OOP is an "implementation detail".

> (often for testing purposes).

Covered in adjacent topics.

> --
> Robert C. Martin (Uncle Bob)��| email:
> Object Mentor Inc.� � � � � ��| blog:��

-T- Received on Thu Mar 06 2008 - 22:23:41 CET

Original text of this message