Tom Lane wrote:
> Craig Ringer <craig@postnewspapers.com.au> writes:
>
>> Tom Lane wrote:
>>
>>> Craig Ringer <craig@postnewspapers.com.au> writes:
>>>
>>>> Speaking of this sort of support tool, what I personally often wish for
>>>> is unique error message identifiers that can be looked up (say, with a
>>>> web form) or a way to un/re-translate localized messages.
>>>>
>>> The VERBOSE option already gives an exact pointer into the backend
>>> sources...
>>>
>>>
>> The trouble is getting people to use it.
>>
>
> Sure, but what's your point? They won't provide a unique message
> identifier without being pushed, either. (No, having such a thing
> displayed by default isn't going to happen.)
Indeed. I was thinking of something like that appearing in default error
messages, otherwise I agree it'd be useless. It's just casual
speculation anyway, bought on by the previous discussion and thinking
about the fact that when working under Windows I actually find the VC++
`C' error codes _useful_.
I'm more interested in re-translating messages, which I'll be having a
bash at shortly. It's hardly important either (it's often possible to
just figure it out given the context, or use the horribly mangled result
from google translate to guess) but might be handy if it proves easy to
put together.
--
Craig Ringer
