One of the advantages of Java in Oracle is eliminating network latency
in situations, where it's difficult to express a batch job in PL/SQL:
http://www.informit.com/articles/article.aspx?p=170870
On May 13, 10:10 am, Jess Holle wrote:
> Java within Oracle is a different beast than what you're us
In general, it's time to raise the abstraction layer around data
storage and retrieval. Millions of developers have been fighting the
impedance mismatch between relational data and object graphs. Instead
of aiming for SQL dialect neutrality as we've typically done in the
JEE world, we really should
Java within Oracle is a different beast than what you're used to in some
ways.
For instance, as I recall the classloaders are isolated to a transaction
and so any classes used are reloaded in each transaction, which can
really kill performance if you have a lot of classes to load to
accomplis
I agree that doing your own IO work inside a relational DB is not a
good thing. But what about the general idea of being able to define
and manipulate objects next-door to a relational world? What about
putting your object-relational mapping into something like Oracle?
Having available garbage co
I'm in a shop where I have PL/SQL devs, Java devs, C# devs, HMTL/
JavaScript web devs, Adobe Flex devs, and combinations thereof.
On the Oracle back-end - the Oracle RAC is expensive to license and
although it offers some HA (you can take a server node in and out of
the database cluster), it real
Personally, I can't wait for SQL/J to come back and get the respect it
deserved -- it was AWESOME.
public void showEmployeeWithJob(String vJob, Java.sql.Timestamp vDate) {
String vName; int vSalary;
#sql { SELECT Ename, Sal
INTO :vName, :vSalary
FROM Emp
WHERE
Many years ago (2001) I was writing my "Java Performance Reports", and
I received this email. I never disclosed this (although it's not that
a big deal), but it's never too late -
"Hi Osvaldo, I was cruising the web when I encountered your article on
JavaLobby. I noticed that you referred to Oracl
No doubt, Oracle has a vested interests in making their DBMS's into
application servers rather than just a dumb data-store, that's
essentially what PL/SQL was about. Furthermore, I think Oracle would
just lve for more ways to offer upgrades to the latest and
greatest embedded JVM version - that
