From: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
To: Neil Conway <neilc@samurai.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Upgrading the backend's error-message infrastructure
Date: Fri, 14 Mar 2003 10:18:48 +0800
Message-ID: <0d1b01c2e9d0$0d265300$6500a8c0@fhp.internal> (raw)
References: <9168.1047588660@sss.pgh.pa.us>
<1047591570.356.1854.camel@tokyo>
> Great work, Tom!
>
> While we're effectively changing every elog call site in the backend,
> would it also be a good idea to adopt a standard for the format of error
> messages? (e.g. capitalization, grammar, etc.)
I 100% agree with this - a style guide!
Chris
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: chriskl@familyhealth.com.au, neilc@samurai.com, tgl@sss.pgh.pa.us, pgsql-hackers@postgresql.org
Subject: Re: Upgrading the backend's error-message infrastructure
In-Reply-To: <0d1b01c2e9d0$0d265300$6500a8c0@fhp.internal>
* 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