I totally agree. Somehow I feel like most of the active voices in this list
have decided that the ONLY way to do OO data is to use the common DAO pattern.
While I prefer a less 'Pure OO' for most of my data work, my code is still
more OO then not. When I need a more pure Object, I make it more pure to fit
my needs.



The other silly argument I've read in this thread is that you
must be consistent in your programming, implying that you need to do a fully
tricked out OO design in order to be consistant.

It is possible to be consistant
without following the <insert somone else's favorite pattern here> pattern.



-Sam Curren



--- [email protected] wrote:

> >OO is like normalizing
a DB.  You could go out the 5 or 6th level, but

> >the experts agree that
you never should, because the benefit of full

> >normalization is outweighed
by the cost it creates when you decide you

> >actually need to use this database.

> 

> In my opinion, this is 100% true, and it's a valuable observation.
Since

> most of us have more experience with databases we realize that

>
normalization is a matter of degree, but we're stuck on the idea that

> there
is but one true way to do something OO - even when that takes your

> code
to ridiculous lengths (google "TURNER'S VIEWPOINT: Why Do Java

> Developers
Like to Make Things So Hard?" for some interesting reading

> whilst you're
at it). It's a question of experience: when you

> denormalize a database,
you know that you are making tradeoffs. The

> thing is, you denormalize a
database for convenience and performances'

> sake, but once you've decided
to use a database, you don't then decide

> to store this bit of information
in a text file, and this bit of

> information in the registry, and this other
bit of information in a

> binary file, etc etc.

> 

> and btw, i've worked
for a boss who **always** went for the quick and

> dirty fix.

> 

> /t

> 

> 

> ----------------------------------------------------------

> You
are subscribed to cfcdev. To unsubscribe, send an email to [email protected]
with the words 'unsubscribe cfcdev' as the subject of the email.

> 

> CFCDev
is run by CFCZone (www.cfczone.org) and supported by CFXHosting 
(www.cfxhosting.com).

> 

> CFCDev is supported by New Atlanta, makers of BlueDragon

> http://www.newatlanta.com/products/bluedragon/index.cfm

> 

> An archive of the CFCDev list is available at 
> www.mail-archive.com/[email protected]

> 

> 

> 


----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to 
[email protected] with the words 'unsubscribe cfcdev' as the subject of the 
email.

CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting 
(www.cfxhosting.com).

CFCDev is supported by New Atlanta, makers of BlueDragon
http://www.newatlanta.com/products/bluedragon/index.cfm

An archive of the CFCDev list is available at 
www.mail-archive.com/[email protected]


Reply via email to