Tom Lane wrote:
> Volkan YAZICI <volkan.yazici@gmail.com> writes:
> > Returned column names from the backend were lowercased by the server
> > in this or that way. Furthermore, PQfnumber() makes not-quoted strings
> > downcasing on the client side and then performs the compare by using
> > the results returned from the backend. To sum up, at the moment I
> > couldn't see any possible solution for this TODO. (I'll be appreciated
> > to hear your suggestions on the case.) An un-fixable situation?
>
> Really, PQfnumber shouldn't do any case folding at all; that's not in
> its charter if you ask me. The problem is how to get there from here
> without too much compatibility pain. Maybe invent a new routine that
> does it right and then deprecate the existing one?
TODO updated:
* Prevent PQfnumber() from lowercasing unquoted the column name
PQfnumber() should never have been doing lowercasing, but historically it has so we need a way to prevent it
-- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610)
359-1001+ If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square,
Pennsylvania19073