Re: enhanced error fields

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: enhanced error fields
Дата
Msg-id CA+TgmoYQiwLXbh+E+0-NU6BKx8fkvG_-_3LwoSmBgHaA_iP1hw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: enhanced error fields  (Peter Geoghegan <peter@2ndquadrant.com>)
Ответы Re: enhanced error fields  ("anarazel@anarazel.de" <andres@anarazel.de>)
Список pgsql-hackers
On Sat, Dec 29, 2012 at 4:30 PM, Peter Geoghegan <peter@2ndquadrant.com> wrote:
> Ascertaining the identity of the object in question perfectly
> unambiguously, so that you can safely do something like lookup a
> comment on the object, seems like something way beyond what I'd
> envisioned for this feature. Why should the comment be useful in an
> error handler anyway? At best, that seems like a nice-to-have extra to
> me. The vast majority are not even going to think about the ambiguity
> that may exist. They'll just write:
>
> if (constraint_name == "upc")
>     MessageBox("That is not a valid barcode.");

The people who are content to do that don't need this patch at all.
They can just apply a regexp to the message that comes back from the
server and then set constraint_name based on what pops out of the
regex.  And then do just what you did there.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Pavel Stehule
Дата:
Сообщение: Re: lock AccessShareLock on object 0/1260/0 is already held
Следующее
От: "anarazel@anarazel.de"
Дата:
Сообщение: Re: enhanced error fields