Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> >>> Should we create some user-friendly macros for the error field codes?
>
> > I was actually talking of the single-letter codes that are used on the
> > protocol layer to tag the different fields of an error or notice result.
>
>
Peter Eisentraut <[EMAIL PROTECTED]> writes:
>>> Should we create some user-friendly macros for the error field codes?
> I was actually talking of the single-letter codes that are used on the
> protocol layer to tag the different fields of an error or notice result.
Oh, those things. Sure, if yo
Tom Lane writes:
> > Should we create some user-friendly macros for the error field codes? I
> > have a feeling that PGXYZ_SQLSTATE may make for better code than just 'C'.
>
> I just pushed the ERRCODE_ macros out into their own file. How about
> placing that file where client apps can include i
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Should we create some user-friendly macros for the error field codes? I
> have a feeling that PGXYZ_SQLSTATE may make for better code than just 'C'.
I just pushed the ERRCODE_ macros out into their own file. How about
placing that file where client
Should we create some user-friendly macros for the error field codes? I
have a feeling that PGXYZ_SQLSTATE may make for better code than just 'C'.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 2: you can get off all lists at
