Re: BUG #5355: locale incorrectly comma-separates "(null)" - Mailing list pgsql-bugs

From Heikki Linnakangas
Subject Re: BUG #5355: locale incorrectly comma-separates "(null)"
Date
Msg-id 4B8C098D.7070905@enterprisedb.com
Whole thread Raw
In response to BUG #5355: locale incorrectly comma-separates "(null)"  ("Andy Lester" <andy@petdance.com>)
Responses Re: BUG #5355: locale incorrectly comma-separates "(null)"  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-bugs
Andy Lester wrote:
> The following bug has been logged online:
>
> Bug reference:      5355
> Logged by:          Andy Lester
> Email address:      andy@petdance.com
> PostgreSQL version: 8.3.6
> Operating system:   Linux
> Description:        locale incorrectly comma-separates "(null)"
> Details:
>
> In my .psqlrc I have the following (among others)
>
> \pset null '(null)'
> \pset numericlocale on
>
> When I select numeric columns that have NULL values, they show as "(nu,ll)".

Hmm, some of the other formats seem to handle numericlocale even worse :-( :

postgres=# \pset numericlocale on
Showing locale-adjusted numeric output.
postgres=# \pset format latex
Output format is latex.
postgres=# SELECT 1234::numeric, 'foobar' ;
\begin{tabular}{r | l}
\textit{numeric} & \textit{?column?} \\
\hline
1,234 & foo,bar \\
\end{tabular}

\noindent (1 row) \\

(note how 'foobar' got a comma in the middle.)

--
  Heikki Linnakangas
  EnterpriseDB   http://www.enterprisedb.com

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #5356: citext not acting like case insensitive search
Next
From: "David E. Wheeler"
Date:
Subject: Re: BUG #5356: citext not acting like case insensitive search