Re: Do we have a range of SQLSTATE codes assigned for custom use?
От | Pavel Stehule |
---|---|
Тема | Re: Do we have a range of SQLSTATE codes assigned for custom use? |
Дата | |
Msg-id | CAFj8pRCCJT8W-3iLPAcKHhOPUU=nsr0W8X3OwGWydjpDmr_XDQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Do we have a range of SQLSTATE codes assigned for custom use? (Craig Ringer <craig@2ndquadrant.com>) |
Список | pgsql-general |
Hello
User defined exceptions should to use "U0" class We don't use it - but it should be documented.
I proposed it - http://www.postgresql.org/message-id/Pine.LNX.4.44.0506160954430.8754-100000@kix.fsv.cvut.cz
but our implementation is less restrictive
Regards
Pavel Stehule
2014-03-24 2:42 GMT+01:00 Craig Ringer <craig@2ndquadrant.com>:
Hi all
With RAISE supporting user-defined SQLSTATEs, and EXCEPTION ... WHEN
supporting matching them, shouldn't we explicitly declare a range of
SQLSTATEs as reserved for custom use?
Right now, there's nothing in
http://www.postgresql.org/docs/current/static/errcodes-appendix.html to
tell a user which SQLSTATE codes they can use without any risk that
PostgreSQL will later use that code for something else.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
В списке pgsql-general по дате отправления: