From: Fabian Streitel <karottenreibe@...>
Date: 2009-08-13T15:37:59+09:00
Subject: Re: Destroying related objects doubt ... basic oop question

--000325558d920843040471002dc4
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

> It was shown (30 years ago) that assembler is noticeably less productive
> than 3GLs
> and therefore should only be used where ultimate cpu control is
> essential.


well, i'm faster making three dumb classes with an orm and calling 3 class
methods with 2 parameters
than setting up and maintaining a database myself and figuring out every
single SQL statement myself
and handling the returned raw data on my own.

so what's your point? first you say we shouldn't use orm, it gives us too
litte control, now you
reject control in favor of effectiveness... :-)

also, orm offer great features besides mapping objects to database entities,
e.g. they help
preventing sql injection and provide tested features for input validation.


Peter: great analysis. I have to agree. one surely has to consider what the
application one works
on needs. rejecting either approach without even considering is not a good
choice. but i certainly
think that most plain vanilla web apps (for which i think the orm issue is
most popular) do very
well with it. the problems that using an orm brings IMHO only arise when
your application reaches
a certain complexity at which level the lost control needs to be reclaimed
to ensure performance,
maintainability, functionality etc., or does anyone have different
experiences?

Greetz!

--000325558d920843040471002dc4--