Re: Turkish downcasting in PL/pgSQL

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: ntufar <ntufar(at)pisem(dot)net>
Cc: pgsql-bugs(at)postgresql(dot)org, Peter Eisentraut <peter_e(at)gmx(dot)net>
Subject: Re: Turkish downcasting in PL/pgSQL
Date: 2004-08-12 19:27:29
Message-ID: 12619.1092338849@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

ntufar <ntufar(at)pisem(dot)net> writes:
> I attached a diff of fix that adds LANG=C; before call to $(FLEX).
> Fixes the problem here but I don't know if adding environment variable
> assignment like this is appropriate. I am not too fluent in PostgreSQL
> build environment and do not know where one can put a global deffinition
> you are talking below.

Um, the attachment was unreadable :-( but I get the idea.

As for the global solution, I was wondering if it would work to put
"LANG=C" right inside the definition of $(FLEX). That would ensure
the right behavior from all our flex builds without unnecessarily
messing up people's build environments otherwise. I don't know however
whether this would parse properly.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Robert E. Bruccoleri 2004-08-12 19:30:53 Re: Regression failure with PostgreSQL 8beta1 and Intel
Previous Message ntufar 2004-08-12 19:09:11 Re: Turkish downcasting in PL/pgSQL

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert E. Bruccoleri 2004-08-12 19:30:53 Re: Regression failure with PostgreSQL 8beta1 and Intel
Previous Message Chris Browne 2004-08-12 19:14:23 Asserting existing key to be primary