From: Josh Berkus <josh@agliodbs.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-docs@postgresql.org
Subject: Re: Error message listing?
Date: Thu, 7 Aug 2003 16:33:55 -0700
Message-ID: <200308071633.55336.josh@agliodbs.com> (raw)
In-Reply-To: <9659.1060298474@sss.pgh.pa.us>
References: <200308071604.19919.josh@agliodbs.com>
<9659.1060298474@sss.pgh.pa.us>
Tom,
> Or were you looking for src/include/utils/errcodes.h ?
More or less.
The issue is that many projects have internal code to handle PG error messages
by parsing them for certain text. The overhaul of message handling is going
to break that code; users need to know what the new messages and/or codes are
before migrating.
--
-Josh Berkus
______AGLIO DATABASE SOLUTIONS___________________________
Josh Berkus
Complete information technology josh@agliodbs.com
and data management solutions (415) 565-7293
for law firms, small businesses fax 621-2533
and non-profit organizations. San Francisco
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-docs@postgresql.org
Cc: josh@agliodbs.com, tgl@sss.pgh.pa.us
Subject: Re: Error message listing?
In-Reply-To: <200308071633.55336.josh@agliodbs.com>
* 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