Re: ColumnName and ColumnNumber in libpq (C interface) - Mailing list pgsql-interfaces

From Tom Lane
Subject Re: ColumnName and ColumnNumber in libpq (C interface)
Date
Msg-id 16696.1063719986@sss.pgh.pa.us
Whole thread Raw
In response to Re: ColumnName and ColumnNumber in libpq (C interface)  (Alberto Cabello Sanchez <alberto@unex.es>)
Responses Re: ColumnName and ColumnNumber in libpq (C interface)  (Alberto Cabello Sanchez <alberto@unex.es>)
List pgsql-interfaces
Alberto Cabello Sanchez <alberto@unex.es> writes:
> On Mon, Sep 15, 2003 at 10:48:47AM -0400, Tom Lane wrote:
>> I wonder whether this behavior is appropriate for PQfnumber, though.
>> It's never been documented ... and certainly should be if we decide
>> we should keep it.  Comments?

> I think PQfnumber(res,PQfname(res,0))==-1 should_never_happen (c) with a
> valid PGresult * res.

> Maybe PQfname(res,0) should be "\"Bar\"", not "Bar".

I don't really want to change PQfname; that would probably break more
apps than changing PQfnumber.

We could achieve the property you suggest if we forgot about
case-insensitive matching and dequoting, and simply made PQfnumber check
for an exact match.

Or we could try some combination behavior (say, try exact match, then
if no luck apply the dequote/downcase logic).  This might offer better
backwards compatibility, but the more complex the behavior, the more
potential for surprising corner cases ...
        regards, tom lane


pgsql-interfaces by date:

Previous
From: Christoph Haller
Date:
Subject: Re: Replicate database
Next
From: Robert Treat
Date:
Subject: Re: Trigger updates MS SQL table