Re: "We don't do triggers"

"Frank" <fbortel_at_nescape.net> schrieb im Newsbeitrag news:bq7a4f$itk$1_at_news1.tilbu1.nb.home.nl...
> Volker Hetzer wrote:
> > "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
> SQL Server has Java in the db? Since when.
It doesn't? Well, it's microsoft after all... One more reason not to have anything to do with it.

> And Orace seems to have plans to remove it from the db.
Just had a short look, didn't see anything about it. Where did you get it from?

Back to topic, so your sole motivation is to use some server to get around portability problems? In that case you've got two solutions:
- Mysql. Get it for your platform and you're done. Fast,

   reliable, supports replication, etc.
- I'm not sure but I think, for portability problems there ought

   to exist much slimmer solutions than a full blown appserver.

Greetings!
Volker Received on Fri Nov 28 2003 - 05:56:31 CST