| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, ntufar <ntufar(at)pisem(dot)net> |
| Cc: | pgsql-bugs(at)postgresql(dot)org, devrim(at)tdmsoft(dot)com |
| Subject: | Re: Turkish downcasting in PL/pgSQL |
| Date: | 2004-08-14 08:21:33 |
| Message-ID: | 200408141021.33455.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Tom Lane wrote:
> Peter, any thoughts on this one way or the other? At the moment
> plpgsql's scan.l seems to be the only use of '%option
> case-insensitive' but we have enough flex lexers laying about that I
> wouldn't be surprised to have this same risk elsewhere. Is it
> reasonable to try to force LANG=C in some global fashion during the
> build?
You'd have to set LC_ALL=C to be really sure to override everything.
But I would stay away from doing that globally, because all the
translation work in gcc and make would go to waste.
I would also suggest that Nicolai report this issue to the flex
developers. It's only bound to reappear everywhere case-insensitive
flex scanners are used.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2004-08-14 08:34:38 | Re: Turkish downcasting in PL/pgSQL |
| Previous Message | Tom Lane | 2004-08-14 02:50:26 | Re: Primary key duplicates |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gaetano Mendola | 2004-08-14 08:28:11 | Re: Calling PL functions with named parameters |
| Previous Message | Gaetano Mendola | 2004-08-14 08:16:27 | Re: Calling PL functions with named parameters |