From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Jeremy Lowery <jslowery(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: to_number, to_char inconsistency. |
Date: | 2013-02-10 23:27:02 |
Message-ID: | 15740.1360538822@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Jeremy Lowery <jslowery(at)gmail(dot)com> writes:
> I load and dump text files with currency values in it. The decimal in these
> input and output formats in implied. The V format character works great for
> outputing numeric data:
> # select to_char(123.45, '999V99');
> to_char
> ---------
> 12345
> (1 row)
> However, when importing data, the V doesn't do the same thing:
> # select to_number('12345', '999V99');
A look at the source code shows that to_number doesn't do anything at
all with the V format code, so this isn't terribly surprising. It
wouldn't be very hard to make it do the right thing, probably, but
nobody's had that particular itch yet. Feel free to scratch it and
send a patch ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Taylor | 2013-02-10 23:36:33 | Re: var/log/postgresql deletion mystery Ubuntu 12.10 |
Previous Message | Noah Misch | 2013-02-10 21:02:59 | Re: BUG #7493: Postmaster messages unreadable in a Windows console |