Re: timestamp format bug - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: timestamp format bug
Date
Msg-id 47A1995D.EE98.0025.0@wicourts.gov
Whole thread Raw
In response to timestamp format bug  ("Roberts, Jon" <Jon.Roberts@asurion.com>)
Responses Re: timestamp format bug  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
>>> On Thu, Jan 31, 2008 at  9:34 AM, in message
<1A6E6D554222284AB25ABE3229A92762715521@nrtexcus702.int.asurion.com>, "Roberts,
Jon" <Jon.Roberts@asurion.com> wrote:
> select to_char(date, 'yyyy-mm-dd hh24:mi:ss.ms') as char,
>        date
>   from (select timestamp'2008-01-30 15:06:21.560' as date) sub
>
> "2008-01-30 15:06:21.560";"2008-01-30 15:06:21.56"
>
> These two fields should be consistent because they should be formatted
> the same way.
Why would you think that?
I would expect the timestamp to be presented with one to nine
digits to the right of the decimal point, depending on the value.
I can think of a couple database products which only go to three
decimal positions, and always show three, but that's hardly a
standard.
-Kevin




pgsql-hackers by date:

Previous
From: "Roberts, Jon"
Date:
Subject: timestamp format bug
Next
From: Hubert FONGARNAND
Date:
Subject: Re: BUG: type of "xxxx" does not match that when preparing the plan