<p><font size="2">> Tom Lane wrote:<br /> ><br /> > Hmm. Not only is that a pretty short list, but many of
themdon't<br /> > correspond very closely to the errors that Postgres would raise.<br /><br /> I think these where
likepredefined 'shortcuts' for most common<br /> exceptions/errors. You can declare exceptions for any oracle error
number<br/> smth. like PRAGMA EXCEPTION_INIT(rollback_too_small, -1555)<br /><br /> >> PL/SQL allows users to
defineand raise their own exceptions too.<br /> ><br /> >Yeah. Our RAISE statement really needs a lot of work,
butI think it<br /> >will have to be left for a future release cycle ...<br /><br /> Sorry, if the following doesn't
makesense, I started exploring just a week ago...<br /><br /> From reading the docs I could't determine what would be
theexception to<br /> catch in the outer block for e.g. RAISE NOTICE 'caught division_by_zero';<br /> and how to raise
thesame exeption again, for example<br /> if I determine that the exception still cannot be handled correcly<br /> in
WHENOTHERS section. Does RAISE raise the same exception or<br /> can I specify the type somehow?<br /><br /> Andre<br
/></font>
