Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> Re: standards
Unfortunately I am not 'selecting' anything ... all the code is 'exec immediate' style.
I know what you are trying to say, but in my requirements I'd rather _ignore_ it than ponder over
it.
Raj
> re: not using "when others then null;"
>
> >> I use it on a regular basis in certain code of mine (on production database that runs 24x7)
> when I
> >> DON'T want the exception to kill the processing.
>
> >not to mention Forms programs. Mighty handy when in-line select statements (not
> >in an explicit begin/end block) start to give off more than one row...
>
> Well, if you are getting more than one row back for that select statement, then your expectation
> of what data would exist does not match what data actually exists. I think hiding that is a
> serious mistake!
> Much better to discover the problem and fix the code to correctly handle the situation rather
> than ignore it.
>
>
> ----------------------------------------------------------------
> Please see the official ORACLE-L FAQ: http://www.orafaq.com
> ----------------------------------------------------------------
> To unsubscribe send email to: oracle-l-request_at_freelists.org
> put 'unsubscribe' in the subject line.
> --
> Archives are at http://www.freelists.org/archives/oracle-l/
> FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
> -----------------------------------------------------------------
>
-- Archives are at http://www.freelists.org/archives/oracle-l/ FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------Received on Thu Aug 05 2004 - 07:32:22 CDT
![]() |
![]() |