Peter Eisentraut <[EMAIL PROTECTED]> writes:
> So would anyone object if I get rid of this while doing the i18n pass over
> libpq?
Don't forget to fix the numerous places where examples of these messages
appear in the documentation ...
regards, tom lane
-
> Most, or at least half, of the error messages that libpq itself generates
> look like "PQwhatever(): this and that went wrong", where PQwhatever is
> usually the function that generates the error message.
>
> I consider this practice ugly. If PQwhatever is an exported API function,
> then the
Most, or at least half, of the error messages that libpq itself generates
look like "PQwhatever(): this and that went wrong", where PQwhatever is
usually the function that generates the error message.
I consider this practice ugly. If PQwhatever is an exported API function,
then the users knows
