Re: Conflicted names of error conditions.
От | Dmitriy Igrishin |
---|---|
Тема | Re: Conflicted names of error conditions. |
Дата | |
Msg-id | AANLkTi=CKNy3-WTwHyqh1Lw-65yQvjMkwHc0Wu_r_y9b@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Conflicted names of error conditions. (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-hackers |
Thanks for you answer, Tom!
I've implemented mapping between SQLSTATE codes and C++ exception
classes of my library. And of course, I've resolved the conflict of names
by giving a proper name to my classes.
Regards,
Dmitriy
2010/8/16 Tom Lane <tgl@sss.pgh.pa.us>
I've implemented mapping between SQLSTATE codes and C++ exception
classes of my library. And of course, I've resolved the conflict of names
by giving a proper name to my classes.
Regards,
Dmitriy
2010/8/16 Tom Lane <tgl@sss.pgh.pa.us>
Yup, that's what the SQL standard calls them :-(. In practice, eitherDmitriy 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?
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 по дате отправления: