From: | Dmitriy Igrishin <dmitigr(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Conflicted names of error conditions. |
Date: | 2010-08-16 18:50:08 |
Message-ID: | AANLkTi=CKNy3-WTwHyqh1Lw-65yQvjMkwHc0Wu_r_y9b@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)sss(dot)pgh(dot)pa(dot)us>
> Dmitriy Igrishin <dmitigr(at)gmail(dot)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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-08-16 18:50:35 | Re: Git migration timeline |
Previous Message | Magnus Hagander | 2010-08-16 18:48:18 | Re: Todays git migration results |