Re: pgsql-server/ oc/src/sgml/libpq.sgml rc/interf ...

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql-server/ oc/src/sgml/libpq.sgml rc/interf ...
Date: 2003-08-24 21:21:05
Message-ID: 603.1061760065@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

petere(at)svr1(dot)postgresql(dot)org (Peter Eisentraut - PostgreSQL) writes:
> Modified files:
> doc/src/sgml : libpq.sgml
> src/interfaces/ecpg/ecpglib: connect.c error.c
> src/interfaces/libpq: libpq-fe.h

> Log message:
> Add macros for error result fields to libpq.

libpq has several internal uses of the error-field codes that perhaps
ought to be converted to use these macros, eg, pqInternalNotice(),
pqGetErrorNotice2(), pqGetErrorNotice3().

More generally, is libpq the right place to declare these? Shouldn't
we instead put 'em in postgres_ext.h, and teach the backend code to use
'em too?

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut - PostgreSQL 2003-08-24 21:26:35 pgsql-server/src/bin/psql/po de.po
Previous Message Peter Eisentraut - PostgreSQL 2003-08-24 21:18:53 pgsql-server/src backend/po/ru.po bin/pg_contr ...