A reader, February 07, 2002 - 6:55 pm UTC
rumors of desupporting java in database
A reader, July 17, 2003 - 12:47 pm UTC
Hi Tom
I have heard rumors that Oracle may be planning
to desupport java in database in future?
Have you heard anything of this sort?
Thanx for this awesome site!
Menon:)
July 17, 2003 - 3:45 pm UTC
no, not true. we moved the j2ee containers out of the database into the middle tier but java in the db is alive and kicking
thanx!
A reader, July 17, 2003 - 3:51 pm UTC
btw, why was the decision made to move the j2ee containers
out of db? performance reasons? Any urls that discuss
this issue would be great!
Thank you!
Menon:)
July 17, 2003 - 4:03 pm UTC
no urls, just practical reasons -- performance being one.
A reader, July 21, 2003 - 4:58 am UTC
jsp = java server page
and there I was thinking it meant
Jackson's method of Structured Programming.
Multi threading
Phil, November 05, 2003 - 4:34 am UTC
from above "A java stored procedure
could be multi-threaded (that is supported) however it is not recommended at
all. It is recommended you do not use threads in a java stored procedure."
why is it recommended you do not use threads in a java stored procedure?
thanks
November 05, 2003 - 8:40 am UTC
because only one thread at a time really runs at a time. java stored procedures should be
a) simple
b) to the point
c) very very small
d) doing only that which plsql cannot do
so they really don't need threads anyway.
JSP
Tony Andrews, November 05, 2003 - 11:20 am UTC
<QUOTE>
java stored procedures should be
a) simple
b) to the point
c) very very small
d) doing only that which plsql cannot do
</QUOTE>
Good advice. However, I worry that those that like Java especially will tend to merely use JSPs instead of PL/SQL procedures as a matter of course.
Where I currently work we have a very mature application that does a lot of its core database work in Pro*C, merely because stored procedures weren't around when it was first written. I heard recently there were plans for a rewrite - in Java! The reason given was that there are more Java programmers in the "market" than PL/SQL programmers. What kind of stupid reason is that?
November 05, 2003 - 6:17 pm UTC
ask them how many DATABASE programmers there are - and what language they program in.
Dime a Dozen
Dan Clamage, November 05, 2003 - 4:12 pm UTC
They're thinking, more = cheaper. Like VB programmers, dime a dozen. They may also be thinking, who will be maintaining the system in 10 years?
I read one performance test between Java and PL/SQL. For database-intensive work, PL/SQL beat the snot out of Java. For complex calculations, Java was faster. I guess because Java has an optimized math runtime library. If you native-compile PL/SQL, you'll get a huge performance boost.
November 06, 2003 - 7:29 am UTC
wait'll 10g ;) then there goes that math argument too
To Tony:
Jens, November 06, 2003 - 7:04 am UTC
Tony Andrews from London, UK wrote:
<QUOTE>
The reason given was that there are more Java programmers in the "market"
than PL/SQL programmers. What kind of stupid reason is that?
</QUOTE>
What a bad decision! But Oracle has pushed it sometimes ago when 99% of every Oracle magazine was full of Java: Jave here and Java there and nobody wants to hear about new features in the databse or pl/sql. If you pick up some of these "more Java programmers from the market" you take somebody in your team who has perhaps a good java knowledge but a bad understanding of the database und query processing and so on. I met a lot of good java programmmers who made a good job as database-performance-killer!
Somebody who knows PL/SQL has a better knowledge in Oracle and helps you to bring back the licence costs of your oracle installation into your company needs. But for these only-java-guys you don't need oracle.
Bye,
Jens
Bye,
Jens
Why Java Stored Procedure
Arindam Mukherjee, October 31, 2006 - 9:09 am UTC
Respected Mr. Tom,
Right now I am learning Java Stored Procedure due to my project requirement. They use this for batch processing. I could not understand why I should use Java Stored Procedure when PL/SQL is enough to get same mileage. Whats the benefit of this over Pl/SQL procedure?
Regards,
October 31, 2006 - 9:59 am UTC
you have hit the nail on the head here.
Indeed, what ARE the advantages?
PLSQL is almost certainly the language you should be using here for "batch processing". Java would be somewhat less efficient to code and process the data with.