Received: from golem.jpl.nasa.gov (IDENT:root@hectic-2.jpl.nasa.gov [128.149.68.204]) by hub.org (8.9.1/8.9.1) with ESMTP id KAA22391 for ; Tue, 27 Oct 1998 10:02:00 -0500 (EST) (envelope-from lockhart@alumni.caltech.edu) Received: from alumni.caltech.edu (localhost [127.0.0.1]) by golem.jpl.nasa.gov (8.8.5/8.8.5) with ESMTP id PAA05231; Tue, 27 Oct 1998 15:02:43 GMT Sender: tgl@mythos.jpl.nasa.gov Message-ID: <3635E093.311004E1@alumni.caltech.edu> Date: Tue, 27 Oct 1998 15:02:43 +0000 From: "Thomas G. Lockhart" Organization: Caltech/JPL X-Mailer: Mozilla 4.07 [en] (X11; I; Linux 2.0.30 i686) MIME-Version: 1.0 To: Peter T Mount , Aleksey Demakov CC: pgsql-interfaces@postgreSQL.org, Peter T Mount Subject: Re: [INTERFACES] JDBC, Timestamps, and DateStyle References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > > But it is not my main problem since I can set DateStyle by myself. > > The other problem is that the driver simetimes fails to parse > > timestamps. > > ... The timestamp can contain fractions of second. If this is the actual Postgres timestamp data type, it should not be showing fractional seconds afaik. It would be good to be able to handle that, since sometime soon it will become more like the datetime type, but at the moment it is implemented as a "seconds from 1970" integer. So the code which decides whether or not to print fractions should never see a fraction to print... Also, afaik timestamp always prints in the "ISO-8601" format as a feature from the original implementer. I think he was wanting some M$ interoperability. I kept that convention when I rewrote the I/O for the data type, but I'm not sure if it is desirable in the long run. Are you _sure_ you are talking about the timestamp type?? - Tom