From: Tom Lane <tgl@sss.pgh.pa.us>
To: Darko Prenosil <darko.prenosil@finteh.hr>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Upgrading the backend's error-message infrastructure
Date: Fri, 14 Mar 2003 10:33:05 -0500
Message-ID: <21328.1047655985@sss.pgh.pa.us> (raw)
In-Reply-To: <200303141229.32585.darko.prenosil@finteh.hr>
References: <9168.1047588660@sss.pgh.pa.us>
<200303141229.32585.darko.prenosil@finteh.hr>
Darko Prenosil <darko.prenosil@finteh.hr> writes:
> What about user messages ?
> If I remember correct, MSSQL had a system catalog table with formated error
> messages, and it was possible to raise error with error number and it's
> parameters. It can be very useful when you must raise same error from
> different places in the code.
But that's exactly the direction we are *not* going in. We had that
discussion a long time ago when we first started internationalizing
our error messages. Peter Eisentraut convinced everybody that we did
not want to tie error codes to unique error messages. [digs in archives
...] See for example
http://fts.postgresql.org/db/mw/msg.html?mid=1279991
I have no desire to revisit that choice.
There is nothing to stop you from creating your own user-defined
messages, and even adding them to the .po files in your installation
if the need strikes. We aren't going to store them in any system table,
however.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, darko.prenosil@finteh.hr, pgsql-hackers@postgresql.org
Subject: Re: Upgrading the backend's error-message infrastructure
In-Reply-To: <21328.1047655985@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox