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 eBDGDxp19849 for ; Wed, 13 Dec 2000 11:13:59 -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 QAA19073 for ; Wed, 13 Dec 2000 16:14:00 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 QAA19067 for ; Wed, 13 Dec 2000 16:14:00 GMT Received: from madweed.ncsc.mil (bluesclues [144.51.154.12]) by madweed.ncsc.mil with ESMTP id LAA29226 for ; Wed, 13 Dec 2000 11:18:58 -0500 Message-ID: <3A37A043.C8EAFDA8@madweed.ncsc.mil> Date: Wed, 13 Dec 2000 16:13:55 +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/111 X-Sequence-Number: 455 This does seem to be a thorny problem. It seems we need an answer that does the following: follows the ISO date style maintains the Postgres milliseconds returns valid records when a select is done based on a Timestamp` Best 2 out of 3? Return milliseconds from the Postgres back end. Ken