Re: How TODO prevent PQfnumber() from lowercasing?

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Volkan YAZICI <volkan(dot)yazici(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: How TODO prevent PQfnumber() from lowercasing?
Date: 2005-10-13 01:23:59
Message-ID: 200510130123.j9D1NxJ06144@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Volkan YAZICI <volkan(dot)yazici(at)gmail(dot)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(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2005-10-13 01:27:46 Re: A costing analysis tool
Previous Message Kevin Brown 2005-10-13 00:46:17 Re: GRANT/roles problem: grant is shown as from login role