From: | Andrew Chernow <ac(at)esilo(dot)com> |
---|---|
To: | David Fetter <david(at)fetter(dot)org> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Better auth errors from libpq |
Date: | 2008-09-12 16:48:31 |
Message-ID: | 48CA9D5F.6060304@esilo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
David Fetter wrote:
> On Fri, Sep 12, 2008 at 12:30:12PM -0400, Alvaro Herrera wrote:
>> Joshua D. Drake wrote:
>>> Heikki Linnakangas wrote:
>>>
>>>>> The only thing I would say here is that you point the URL to
>>>>> current which will be wrong in one release. Perhaps something
>>>>> that pulls the pgversion macro?
>>>> We don't put URLs in error messages. The hint needs to be a real
>>>> sentence.
>>> Which is exactly why its the first thing we do when supporting
>>> people. Point them to the URL in the docs.
>> Let's add a new field in error reports: errurl()
>
> Excellent idea :)
>
> Cheers,
> David.
If you start using urls in error messages, it might be helpful to point
everything at a single url and only change the query_string, maybe....
http://www.postgresql.org/docs/?err_id
Not sure if err_id is the correct value for the query_string, but I'm
sure something like the above would simply/centralize management.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
From | Date | Subject | |
---|---|---|---|
Next Message | David E. Wheeler | 2008-09-12 16:50:25 | Re: [Review] Tests citext casts by David Wheeler. |
Previous Message | David Fetter | 2008-09-12 16:45:28 | Re: Better auth errors from libpq |