RE: Options for poorly performing SQL

From: Patterson, Joel <>
Date: Tue, 5 Feb 2013 09:18:08 -0500
Message-ID: <>

Hear hear, we have the same issue, but with Hybernate. The code has to be absolutely ridiculous before it will be replaced, but I believe it actually happened -- that they can 'hard code' sql code in such hot spots. They save[d] boatloads of money because they don't need to hire oracle developers to write the sql :) ... -- cause as we all know, we don't really need all of what sql offers -- we don't need more than Hybernate can do by itself to get the job done.

Joel Patterson
Database Administrator
904 727-2546
-----Original Message-----
From: [] On Behalf Of Andrew Kerber Sent: Monday, February 04, 2013 11:17 AM To:
Cc:; oracle-l
Subject: Re: Options for poorly performing SQL

I have had this problem before, and while part of the problem is most likely the dynamically generated sql, the core of the problem may well be that they simply do not know how to change the code that is generated. I have run into that case before, I identified bad sql, sent it to them, and got no response at all. After some digging I realized that all they really knew was how to work with the Java objects to get data from the database, they had no understanding of where the code was actually coming from, what it said, or how to change it. On Mon, Feb 4, 2013 at 10:03 AM, Carlos Sierra <>wrote:

> <snip>
> --

Andrew W. Kerber

'If at first you dont succeed, dont take up skydiving.'


Received on Tue Feb 05 2013 - 15:18:08 CET

Original text of this message