Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> comp.databases.theory -> Re: The wisdom of the object mentors (Was: Searching OO Associations with RDBMS Persistence Models)

Re: The wisdom of the object mentors (Was: Searching OO Associations with RDBMS Persistence Models)

From: x <x_at_not-exists.org>
Date: Tue, 13 Jun 2006 16:19:19 +0300
Message-ID: <e6mdpo$7vt$1@nntp.aioe.org>

<frebe73_at_gmail.com> wrote in message
news:1150197168.650237.258620_at_p79g2000cwp.googlegroups.com...
> >> I've worked with code where the SQL was "encapsulated" in a seperate
> >> area. It was PAIN in the Arse.
> >
> > I've worked with code where the SQL was embedded throughout. That's a
> > pain in the ass too. The code constantly oscilates between three
> > different languages. (SQL, Tables-rows, code).

> The same thing can be said about modern web development, the code
> oscilates between HTML, JavaScript and server-side scripting language.
> I think we need different languages for different purposes mixed
> together JSP/ASP/PHP and SQLJ are fine examples of that.

http://en.wikipedia.org/wiki/Tower_of_Babel

> > One system I worked on completely melted down when the DB vendor went
> > out of business. There was no way to find and replace all that SQL
> > (though we tried for 6 months).

> But a decoupled strategy would not descrease the number of SQL
> statements, you just put the statements in a separate layer, or? The
> amount of work for modifying the SQL statements would be the same.

No, because you will not have to search for them (if you are absolutely sure the policy was respected :) Received on Tue Jun 13 2006 - 08:19:19 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US