Re: Java to die in 2003

"Joel Garry" <joel-garry_at_home.com> wrote in message news:91884734.0212311517.78cdcf90_at_posting.google.com... <snip a lot of interesting argument>
> Is it really a good idea
> to re-write stored procedures every time you change a database vendor?
What do you do to support multiple databases?

Actually I think that it is. Of course my experience is coloured by buying third party products that run on a varety of different database platforms. They invariably are demonstrably sub-optimal as far as the database platform that they are running on (Oracle) is concerned. I'd much rather that if you are buying a product that costs as much as RDBMS's cost then products that ran on that product were able to take advantage of the features you just paid all that cash for.

> What if you want to
> join data between databases?

In general I wouldn't. I'd want to either ship data between databases or publish an interface to the data, and call it from some business logic somewhere outside the db.

>
> Isn't PL/SQL an oxymoron, given that SQL is non-procedural?

<G>, Transact-SQL is kind of an interesting name as well thought about in this sort of way.

Cheers

--
Niall Litchfield
Oracle DBA
Audit Commission UK
*****************************************
Please include version and platform
and SQL where applicable
It makes life easier and increases the
likelihood of a good answer
******************************************