Re: Why use Java Stored Procedures....

From: <dbaplusplus_at_hotmail.com>
Date: 3 Mar 2006 18:31:13 -0800
Message-ID: <1141439473.852375.324590@z34g2000cwc.googlegroups.com>

Jim Kennedy wrote:
> "Bob Jones" <email_at_me.not> wrote in message
> news:1NqNf.17162$rL5.14763_at_newssvr27.news.prodigy.net...
> >
> > "HansF" <News.Hans_at_telus.net> wrote in message
> > news:pan.2006.03.01.22.08.14.356624_at_telus.net...
> > > On Wed, 01 Mar 2006 19:09:16 +0000, Gerry Atric wrote:
> > >
> > >> Miggins wrote:
> > >>
> > >>> OK short question but probably not a quick answer....anyone give me
> the
> > >>> pros and cons of using Java for my stored proedures instead of PLSQL.
> > >>
> > >>
> > >>
> > >> CON: PL/SQL is 100% Oracle-centric while Java is not. If you ever want
> > >> to
> > >> migrate your apps away from Oracle for some reason, keep in mind that
> all
> > >> of your PL/SQL code will have to be ported too. My personal rule of
> > >> thumb,
> > >> anything I develop in PL/SQL I do with the assumption that it will
> never
> > >> be
> > >> ported in the future.
> > >
> > > If you copy Oracle-optimized Java stored procedures to other databases
> > > without thinking, the procedure is likely to have performance, locking
> > > or concurrency problems.
> > >
> > > If you did not take advantage of Oracle capabilities, you may be causing
> > > performance issues that can easily result in the need to purchase
> > > additional equipment and additional Oracle licenses. Thus creating the
> > > perception that Oracle is expensive, even though the reason for the
> > > expense is laziness or simple misuse of the environment for the sake of
> > > 'independence'.
> > >
> > >
> > > Therefore, my belief is that using Java - if written properly (cost
> > > effectively) - must be ported in the same sense as PL/SQL ... with
> > > thought.
> > >
> >
> > Would you rather have a Java programmer migrating Java stored procedures
> to
> > a different database or have a PL/SQL programmer migrating PL/SQL stored
> > procedures to a foreign language for a different database?
> >
> >

>

> Java in the database isn't transparent. You have to write pl/sql wrappers
> for all the exposed Java functions and stored procedures. At some point
> writing a few simple if statements is just simpler to do in pl/sql. (than
> create wrapper and write in Java.)

>

> Java has some nice classes for certain types of things. But using it in the
> database to just use it in the database instead of pl/sql is prone to
> problems and ineffeciencies. Use the proper tool for the proper job. (don't
> assume everything is a nail if all you have is a hammer.)
> Jim

I wish Oracle would provide Java natively in database, so one does not have to write PL/SQL as wrapper. I may be biased bit Java is much nicer language than PL/SQL and not limited to database code. With Oracle adding more and more Java (see number of .jar files supplied with Oracle installation) in database and application server,  may be some day Java is available just like PL/SQL.

Today, in reality, it is hard to find many applications where one will write Java stored procedures. If one wants to do complex database logic, one can do it outside Java stored procedures. However, if Java was supported similar to PL/SQL many more people may use it. Received on Fri Mar 03 2006 - 20:31:13 CST