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 f3L3B7348543
	for <pgsql-interfaces@postgresql.org>;
	Fri, 20 Apr 2001 23:11:07 -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 UAA01803
	for <pgsql-interfaces@postgresql.org>; Fri, 20 Apr 2001 20:11:04 -0700
Message-ID: <003901c0ca10$b301c8e0$5a2b7ad8@expertrade.com>
Reply-To: "David Wall" <d.wall@computer.org>
From: "David Wall" <d.wall@computer.org>
To: <pgsql-interfaces@postgresql.org>
Subject: Java timestamps
Date: Fri, 20 Apr 2001 20:11:03 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0036_01C0C9D6.06922800"
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: 200104/94
X-Sequence-Number: 1478

This is a multi-part message in MIME format.

------=_NextPart_000_0036_01C0C9D6.06922800
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

According to the docs, the PostgreSQL TIMESTAMP is accurate to microseconds=
.  But the typical display only goes to centiseconds.  Java and Unix timest=
amps generally go to milliseconds.

Is there a way to get Postgresql 7.1 to report times with higher resolution=
?  As it is, when you store a timestamp via JDBC, you won't get back the sa=
me time you put in because it's missing that last digit of resolution.

Thanks,
David

------=_NextPart_000_0036_01C0C9D6.06922800
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4611.1300" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>According to the docs, the PostgreSQL TIME=
STAMP is=20
accurate to microseconds.&nbsp; But the typical display only goes to=20
centiseconds.&nbsp; Java and Unix timestamps generally go to=20
milliseconds.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Is there a way to get Postgresql 7.1 to re=
port=20
times with higher resolution?&nbsp; As it is, when you store&nbsp;a timesta=
mp=20
via JDBC, you won't get back the same time you put in because it's missing =
that=20
last digit of resolution.<BR><BR>Thanks,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>David</FONT></DIV></BODY></HTML>

------=_NextPart_000_0036_01C0C9D6.06922800--