Re: ColumnName and ColumnNumber in libpq (C interface)
От | Tom Lane |
---|---|
Тема | Re: ColumnName and ColumnNumber in libpq (C interface) |
Дата | |
Msg-id | 16696.1063719986@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: ColumnName and ColumnNumber in libpq (C interface) (Alberto Cabello Sanchez <alberto@unex.es>) |
Ответы |
Re: ColumnName and ColumnNumber in libpq (C interface)
|
Список | 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 по дате отправления: