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

From Tom Lane
Subject Re: pgsql-server/ oc/src/sgml/libpq.sgml rc/interf ...
Date
Msg-id 27368.1065322868@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql-server/ oc/src/sgml/libpq.sgml rc/interf ...  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-committers
Peter Eisentraut <peter_e@gmx.net> writes:
> Tom Lane writes:
>> Document the always-true-but-previously-undocumented fact that PQfnumber()
>> will downcase the supplied field name unless it is double-quoted.  Also,
>> upgrade the routine's handling of double quotes to match the backend,
>> in particular support doubled double quotes within quoted identifiers.

> Isn't that an instance of the same "buggy" behavior that the database name
> provided to libpq once exhibited, i.e., it should be removed?

Well, we can re-discuss it if you like.  I'd have preferred that answer
myself, but it didn't seem to be the winner in the pg-interfaces discussion.


>> Per pgsql-interfaces discussion a couple weeks ago.

> Could I request that technical decisions that are reached somewhere in the
> depth of threads on user-level mailing lists are posted to hackers before
> they are applied?

As far as I'm concerned, pgsql-interfaces is an appropriate and
sufficiently authoritative discussion forum for issues that only affect
the interface libraries and not the backend.  If we aren't willing to
delegate, we might as well eliminate all the other lists and just have
pgsql-hackers.

            regards, tom lane

pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgsql-server/ oc/src/sgml/runtime.sgml rc/back ...
Next
From: momjian@svr1.postgresql.org (Bruce Momjian)
Date:
Subject: pgsql-server/doc FAQ src/FAQ/FAQ.html