From: David Wall <d.wall@computer.org>
To: pgsql-general@postgresql.org
To: pgsql-sql@postgresql.org
Subject: Re: Timestamp Resolution in Postgres
Date: Mon, 7 May 2001 09:20:35 -0700
Message-ID: <015301c0d711$a5c5e680$5a2b7ad8@expertrade.com> (raw)
References: <9cs8hn$125n$1@news.tht.net>
> update table person set birthday = '2001-05-03 11:12:56.343' where
objectid
> = '34';
>
> followed by
>
> select * from person where objectid = '34';
>
> I get :
>
> 2001-05-03 11:12:56.34-07
This is a frustration that I also ran into, but there's no clean way to
handle it, especialy when using JDBC which takes the default String format
for a date, and therefore the thousandth of a second number is always
dropped. It's odd, though, since the database itself claims to support down
to millionths or nanos or some such thing. But I've not heard any mention
about how to change the default format to include more digits.
The alternatives appear to be: 1) don't worry about unless that extra
"resolution" really matters -- you know the system clock is not that
accurate anyway; 2) store it in an INT8/long...
David
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: d.wall@computer.org, pgsql-general@postgresql.org
Subject: Re: Timestamp Resolution in Postgres
In-Reply-To: <015301c0d711$a5c5e680$5a2b7ad8@expertrade.com>
References: <9cs8hn$125n$1@news.tht.net> <015301c0d711$a5c5e680$5a2b7ad8@expertrade.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox