Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.misc -> Re: trapping pl/sql errors with line numbers
"Jeff Smith" <jsmit234 at ford dot com> wrote:
> I don't allow "ungraceful" exits.
Then you have not met ORA-0600 yet.
> It is unhandled in the sense that I didn't expect it. I catch the error,
> record and the caller handle what to do next. It would be nice to be able
> to get details of what the problem is.
I agree. Wrote some very basic DB2 code a long time ago using Delphi, and it was great to have an exception returned that told you _exactly_ where the problem is - instead of receiving something like a meaningless syntax error number without knowing what went wrong where...
> I write good code and work hard to do so, but I don't pretend to not run
> into problems from time to time.
Yeah.. well.. be glad that problems don't just keep on running into you. Ya fix one ORA-0600 and ya get another one. Dammit. Another weekend threatened.
-- BillyReceived on Fri Jun 20 2003 - 10:26:47 CDT
![]() |
![]() |