Tom Lane wrote:
"Eugene Pimenov" <[EMAIL PROTECTED]> writes:
2) Write a code to every translation (e.g. Error 424242 inccorrect ...), so
people can actually google out a solution for their problems.
RTFM:
http://www.postgresql.org/docs/8.3/static/errcodes-appendix.html
PostgreSQL error codes are not as unique as the error messages.
If you don't like translated error messages, you could just set
lc_messages to en_US in your postgresql.conf.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
