From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
---|---|
To: | Andy Lester <andy(at)petdance(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #5355: locale incorrectly comma-separates "(null)" |
Date: | 2010-03-01 18:38:05 |
Message-ID: | 4B8C098D.7070905@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Andy Lester wrote:
> The following bug has been logged online:
>
> Bug reference: 5355
> Logged by: Andy Lester
> Email address: andy(at)petdance(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | David E. Wheeler | 2010-03-01 18:39:03 | Re: BUG #5356: citext not acting like case insensitive search |
Previous Message | Tom Lane | 2010-03-01 18:25:28 | Re: BUG #5356: citext not acting like case insensitive search |