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

From Peter Eisentraut
Subject Re: pgsql-server/ oc/src/sgml/libpq.sgml rc/interf ...
Date
Msg-id Pine.LNX.4.44.0310050102260.2745-100000@peter.localdomain
Whole thread Raw
In response to pgsql-server/ oc/src/sgml/libpq.sgml rc/interf ...  (tgl@svr1.postgresql.org (Tom Lane))
Responses Re: pgsql-server/ oc/src/sgml/libpq.sgml rc/interf ...
List pgsql-committers
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?

>     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?

--
Peter Eisentraut   peter_e@gmx.net


pgsql-committers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: pgsql-server/ oc/src/sgml/runtime.sgml rc/back ...
Next
From: Tom Lane
Date:
Subject: Re: pgsql-server/ oc/src/sgml/runtime.sgml rc/back ...