Title: RE: Different behavior of Too_many_rows exception in pl/sql betwe
if you are looking for one row only, then A and C will do. Since C involves a little bit of more coding and A does the same thing, A would be a better choice. But if you are coding to trap too many rows, then you should
On Fri, Jun 22, 2001 at 12:45:34AM -0800, Amar Kumar Padhi wrote:
if you are looking for one row only, then A and C will do. Since C involves
a little bit of more coding and A does the same thing, A would be a better
choice. But if you are coding to trap too many rows, then you should check
Where is the fun in that? To quote a previous coworker Any clod can have
facts, but having an opinion is an art. Besides, you missed the two key
words of the question: and why? I was hoping to spark a nice extended
discussion on the inner workings of Oracle that everyone could enjoy while
I have seen code that depends on the 8.1 behavior. It does bring up a
question I have always wondered about. The question for the internals
ubergeeks is: which of the following is best to use? (All should have the
same result, so which one has the best performance and why?)
A)
declare
y
I would say that (A) will be the most performant
because you are giving Oracle the EXTRA information
that you only want one row. (b) and (c) could
possibly produce a massive result set of which you
only then fetch 1 row.
hth
connor
--- Norrell, Brian [EMAIL PROTECTED] wrote:
I have seen code
Brian:
Why don't you do what us ubergeeks do? Test. in a loop, try run each
version, say 1000 times and tell us how long they take to run in your
environment.
(I want to know, but am too lazy to do this for myself right now!)
Kevin
-Original Message-
Sent: Thursday, June 21, 2001 4:36
