Thread: Conflicted names of error conditions.

Hey all,<br /><br />According to <a
href="http://www.postgresql.org/docs/9.0/static/errcodes-appendix.html">http://www.postgresql.org/docs/9.0/static/errcodes-appendix.html</a><br
/>someerror conditions has non-unique *names*. There are:<br /> modifying_sql_data_not_permitted,<br
/>prohibited_sql_statement_attempted,<br/>reading_sql_data_not_permitted<br />from <span class="bold"><span
class="EMPHASIS">SQLRoutine Exception and </span></span><span class="bold"><span class="EMPHASIS">External Routine
Exceptionclasses.<br /><br />It should be?<br /><br />Regards,<br />Dmitriy<br /><br /></span></span> 

Dmitriy Igrishin <dmitigr@gmail.com> writes:
> According to
> http://www.postgresql.org/docs/9.0/static/errcodes-appendix.html
> some error conditions has non-unique *names*. There are:
> modifying_sql_data_not_permitted,
> prohibited_sql_statement_attempted,
> reading_sql_data_not_permitted
> from SQL Routine Exception and External Routine Exception classes.

> It should be?

Yup, that's what the SQL standard calls them :-(.  In practice, either
underlying SQLSTATE will match that name in an EXCEPTION block, so
it doesn't matter a whole lot.  If you have a case where you feel it
does matter, you can trap by the SQLSTATE code instead.
        regards, tom lane