Received: from hub.org (hub.org [216.126.84.1]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id e9UFYZC33092 for ; Mon, 30 Oct 2000 10:34:35 -0500 (EST) (envelope-from pgsql-interfaces-owner@mail.postgresql.org) Received: from jazzband.ncsc.mil (jazzband.ncsc.mil [144.51.5.4]) by hub.org (8.10.1/8.11.0) with ESMTP id e9UF2qi35939 for ; Mon, 30 Oct 2000 10:02:52 -0500 (EST) (envelope-from khkachn@madweed.ncsc.mil) Received: from jazzband.ncsc.mil (localhost [127.0.0.1]) by jazzband.ncsc.mil (8.9.1/8.9.1) with ESMTP id PAA27317 for ; Mon, 30 Oct 2000 15:02:39 GMT Received: from madweed.ncsc.mil (madweed.ncsc.mil [144.51.154.21]) by jazzband.ncsc.mil (8.9.1/8.9.1) with ESMTP id PAA27313 for ; Mon, 30 Oct 2000 15:02:38 GMT Received: from madweed.ncsc.mil (bluesclues [144.51.154.12]) by madweed.ncsc.mil with ESMTP id KAA17274 for ; Mon, 30 Oct 2000 10:06:42 -0500 Message-ID: <39FD8E65.4FED4534@madweed.ncsc.mil> Date: Mon, 30 Oct 2000 15:06:13 +0000 From: Ken Kachnowich X-Mailer: Mozilla 4.51 [en] (X11; U; Linux 2.0.35 i686) X-Accept-Language: en MIME-Version: 1.0 To: postgres interfaces Subject: RE: datetime fix Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200010/8 X-Sequence-Number: 8 The Timestamp problem seems to be with the backend truncating the millseconds to 2 digits. Here are the (abreviated) results from my test queries: Inserting record: query: insert into table_a values (91, '2000-10-30 09:19:57.321') psql select: my_db=# select * from table_a; id | message_time --+---------------------- 91 | 2000-10-30 09:19:57.32-05 Note the milleseconds were truncated from .321 to .32 Result from JDBC select of Timestamp field: 91 | 2000-10-30 09:19:57.032 The Timestamp field has been padded to 3 digits but started out with an incorrect value. Could I have something set wrong to cause this or is this a bug? Thanks, Ken