Re: Conflicted names of error conditions. - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Conflicted names of error conditions.
Date
Msg-id 6142.1281974922@sss.pgh.pa.us
Whole thread Raw
In response to Conflicted names of error conditions.  (Dmitriy Igrishin <dmitigr@gmail.com>)
Responses Re: Conflicted names of error conditions.
List pgsql-hackers
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


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: "Bogus data in lock file" shouldn't be FATAL?
Next
From: Tom Lane
Date:
Subject: Re: "Bogus data in lock file" shouldn't be FATAL?