Received: from mail1.expertrade.com (r87-43-dsl.sea.lightrealm.net [216.122.43.87]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f47GKXA68791; Mon, 7 May 2001 12:20:33 -0400 (EDT) (envelope-from d.wall@computer.org) Received: from reggae (reggae.expertrade.com [216.122.43.90]) by mail1.expertrade.com (8.9.3/8.9.3) with SMTP id JAA28832; Mon, 7 May 2001 09:20:32 -0700 Message-ID: <015301c0d711$a5c5e680$5a2b7ad8@expertrade.com> Reply-To: "David Wall" From: "David Wall" To: , References: <9cs8hn$125n$1@news.tht.net> Subject: Re: Timestamp Resolution in Postgres Date: Mon, 7 May 2001 09:20:35 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Archive-Number: 200105/305 X-Sequence-Number: 9086 > 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