From: Þórhallur Hálfdánarson <tolli@tol.li>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: 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 15:54:20 +0000
Message-ID: <20030314155420.A24125@tol.li> (raw)
In-Reply-To: <21328.1047655985@sss.pgh.pa.us>
References: <9168.1047588660@sss.pgh.pa.us>
<200303141229.32585.darko.prenosil@finteh.hr>
<21328.1047655985@sss.pgh.pa.us>
-*- Tom Lane <tgl@sss.pgh.pa.us> [ 2003-03-14 15:33 ]:
> 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.
What about the option of having error numbers unique, but have error numbers linked to error messages (unique in code, but share strings).
Just my .02 ISK.
--
Regards,
Tolli
tolli@tol.li
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: tolli@tol.li, 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: <20030314155420.A24125@tol.li>
* 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