| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Volkan YAZICI <volkan(dot)yazici(at)gmail(dot)com> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: How TODO prevent PQfnumber() from lowercasing? |
| Date: | 2005-10-12 23:06:01 |
| Message-ID: | 5088.1129158361@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-10-12 23:11:12 | Re: Comments on columns in the pg_catalog tables/views |
| Previous Message | Tom Lane | 2005-10-12 22:54:29 | Re: pgsql: Do all accesses to shared buffer headers through |