Re: enhanced error fields
От | anarazel@anarazel.de |
---|---|
Тема | Re: enhanced error fields |
Дата | |
Msg-id | 1d25dc31-e98e-47a0-a91a-e884619f7fbc@email.android.com обсуждение исходный текст |
Ответ на | Re: enhanced error fields (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: enhanced error fields
|
Список | pgsql-hackers |
Robert Haas <robertmhaas@gmail.com> schrieb: >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. Easier said than done if you're dealing with pg installations with different lc_messages... Andres --- Please excuse the brevity and formatting - I am writing this on my mobile phone.
В списке pgsql-hackers по дате отправления: