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 <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
