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

Home -> Community -> Usenet -> c.d.o.misc -> Re: "We don't do triggers"

Re: "We don't do triggers"

From: Volker Hetzer <volker.hetzer_at_ieee.org>
Date: Fri, 28 Nov 2003 10:59:21 +0100
Message-ID: <bq79n5$mse$1@news.fujitsu-siemens.com>

"Frank" <fbortel_at_nescape.net> schrieb im Newsbeitrag news:bq5pa7$bnj$1_at_news1.tilbu1.nb.home.nl...
> Volker Hetzer wrote:
>
> > "Frank" <fbortel_at_nescape.net> schrieb im Newsbeitrag news:bq34ho$qr$1_at_news4.tilbu1.nb.home.nl...
> >
> >>What if you have customers that wish your product to run
> >>on a variaty of backends?
> >>Makes sense to put (1 version!) of the business rules in
> >>the middle tier to me. Use the database just as a pool of data;
> >>no logic
> >
> > What if they wish to use a variety of middle tiers?
> >
> > Greetings!
> > Volker
>
> I tell 'm I don't do that ;-)
> Seriously - the customer can have any middle tier as long as
> it's black - sorry, Java.
>
> The background of all this is simply a matter of
> development cost - it's cheaper (at least, thought to
> be!) to develop the logic in one flavour (Java), than in,
> say two or three (Oracle: PL/SQL, SQL Server: TSQL, DB2/MySQL/...)
But look, who prevents the developer from using java stored procedures in the db if he wants to use java? That's no reason to do an app server!

Greetings!
Volker Received on Fri Nov 28 2003 - 03:59:21 CST

Original text of this message

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