Re: "We don't do triggers"

"Frank" <[EMAIL PROTECTED]> schrieb im Newsbeitrag news:[EMAIL PROTECTED]
> Volker Hetzer wrote:
> > "Frank" <[EMAIL PROTECTED]> schrieb im Newsbeitrag news:[EMAIL PROTECTED]
> > 
> >>Volker Hetzer wrote:
> >>
> >>
> >>>"Frank" <[EMAIL PROTECTED]> schrieb im Newsbeitrag news:[EMAIL PROTECTED]
> >>>
> >>>
> >>>>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? Bad for them.

> And Orace seems to have plans to remove it from the db.
A short google search returned a healthy amount of up-to-date information
on oracle and java. I didn't find anything about removing java. So,
where did you get that from? Anyway, you can do C/C++ as well,
even in a safe way (without crashing the database), so, no problem.

Besides, even if you leave out the whole language thing and limit
yourself to plain sql, you still can't run the same statements on
both servers because the features they offer are simply too
different. Function indexes and bitmap indexes are just two
examples. You might as well leave out the whole database
and limit yourself to plain files handled by a server. Which offers
functions to get at the file text and enforce constraints and
imlement business rules and all that stuff. Uh, well, you know,
basically, like a database server...

Another possibility: You can link the
mysql-libraries into your application server and have one
executable, can link in the customization language of your choice
(Tcl? Perl?) and have the same code running everywhere. Including
the same flavour of SQL on each platform you've ported
your server. How about that?

Lots of Greetings!
Volker