Received: from jazzband.ncsc.mil (jazzband.ncsc.mil [144.51.5.4]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eBBHTim37535 for ; Mon, 11 Dec 2000 12:29:44 -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 RAA08673 for ; Mon, 11 Dec 2000 17:29:44 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 RAA08669 for ; Mon, 11 Dec 2000 17:29:43 GMT Received: from madweed.ncsc.mil (bluesclues [144.51.154.12]) by madweed.ncsc.mil with ESMTP id MAA14978 for ; Mon, 11 Dec 2000 12:34:39 -0500 Message-ID: <3A350EFF.3DB8E924@madweed.ncsc.mil> Date: Mon, 11 Dec 2000 17:29:36 +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: pgsql-interfaces Subject: RE: JDBC Timestamp Problem Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200012/73 X-Sequence-Number: 410 I ran into a Timestamp problem a while back. The Postgres back end seems to return 2 digits for the milliseconds when the JDBC is expecting 3 digits (and 3 digits is correct). I am not sure if this has already been fixed or reported or even if it is the real problem at all. Does anyone know where I could checked to see if a patch is availalbe for this? Thanks, Ken