| From: | Neil Conway <neilc(at)samurai(dot)com> |
|---|---|
| To: | Mahesh Swamy <maheshs(at)fast(dot)fujitsu(dot)com(dot)au> |
| Cc: | osspatches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: SQLState |
| Date: | 2004-05-12 02:56:29 |
| Message-ID: | 1084330589.23490.24.camel@tokyo |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
On Tue, 2004-05-11 at 22:07, Mahesh Swamy wrote:
> 1/ Is there a convention for creating sub-class codes.
The only convention I can see is that subclass values not defined by the
SQL specification begin with 'P'. (This ought to be documented; barring
any objections, I'll commit a patch stating this in errcodes.h
explicitly). Beyond that I don't know of any other conventions.
> 2/ If there is no convention is it ok to use the letter 'x' for all our
> State codes?
Why would you want to do that?
> 2/ If we have some States that might become common to the code in
> future releases, can we give them in as patches?
What's the value in keeping these the same? (If a client is already
looking for a specific error code, it doesn't seem too onerous for them
to need to look for two.)
-Neil
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-05-12 03:44:20 | Re: SQLState |
| Previous Message | Mahesh Swamy | 2004-05-12 02:07:50 | SQLState |