Re: Internationalized error messages

From: Karel Zak <zakkr(at)zf(dot)jcu(dot)cz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Internationalized error messages
Date: 2001-03-09 07:53:20
Message-ID: 20010309085320.A7401@ara.zf.jcu.cz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Mar 08, 2001 at 09:00:09PM -0500, Tom Lane wrote:
> > On Thu, Mar 08, 2001 at 11:49:50PM +0100, Peter Eisentraut wrote:
> >> I really feel that translated error messages need to happen soon.
>
> Agreed.

Yes, error codes is *very* wanted feature.

>
> ERROR: Attribute "foo" not found -- basic message for dumb frontends
> ERRORCODE: UNREC_IDENT -- key for finding localized message
> PARAM1: foo -- something to embed in the localized message
> MESSAGE: Attribute or table name not known within context of query
> CODELOC: src/backend/parser/parse_clause.c line 345
> QUERYLOC: 22

Great idea! I agree that we need some powerful Error protocol instead
currect string based messages.

For transaltion to other languages I not sure with gettext() stuff on
backend -- IMHO better (faster) solution will postgres system catalog
with it.

May be add new command too: SET MESSAGE_LANGUAGE TO <xxx>, because
wanted language not must be always same as locale setting.

Something like elog(ERROR, gettext(...)); is usable, but not sounds good
for me.

Karel

--
Karel Zak <zakkr(at)zf(dot)jcu(dot)cz>
http://home.zf.jcu.cz/~zakkr/

C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zeugswetter Andreas SB 2001-03-09 09:28:14 AW: WAL does not recover gracefully from out-of-disk-sp ace
Previous Message Hiroshi Inoue 2001-03-09 06:33:15 Re: How to handle waitingForLock in LockWaitCancel()