| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Sergei Kornilov <sk(at)zsrv(dot)org> |
| Cc: | "taddeoluca96(at)gmail(dot)com" <taddeoluca96(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #15389: Fill zero in milliseconds of a timestamp |
| Date: | 2018-09-18 13:17:00 |
| Message-ID: | CAKFQuwZjOM4pr5ayBvaev66M6S=fAaeWEvJr=2D0kk7h=BqhGg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tuesday, September 18, 2018, Sergei Kornilov <sk(at)zsrv(dot)org> wrote:
> Hello
>
> > I don't think is correct because if I try to convert in Java become 099.
> "2014-09-26 17:17:45.099"?
> I think Java is incorrect here. Usually trailing zeros can be omitted.
> Also postgresql timestamp has resolution 1 microsecond, so with trailing
> zeros it must be "2014-09-26 17:17:45.990000", not "2014-09-26
> 17:17:45.990".
>
Except the decimal in that construct is a simple part separator and not a
fractional indicator. You cannot drop trailing zeros in the last part in
the same way you cannot drop trailing zeros when describing one hundred
(100) because if you do you get the number one (1) instead.
David J.
.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Gierth | 2018-09-18 13:30:10 | Re: BUG #15389: Fill zero in milliseconds of a timestamp |
| Previous Message | Sergei Kornilov | 2018-09-18 11:59:21 | Re: BUG #15389: Fill zero in milliseconds of a timestamp |