Received: from golem.jpl.nasa.gov (IDENT:root@hectic-1.jpl.nasa.gov [128.149.68.203]) by hub.org (8.9.2/8.9.1) with ESMTP id MAA31679 for ; Mon, 1 Feb 1999 12:31:04 -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 RAA14102; Mon, 1 Feb 1999 17:30:48 GMT Sender: tgl@mythos.jpl.nasa.gov Message-ID: <36B5E4C7.1BEC1645@alumni.caltech.edu> Date: Mon, 01 Feb 1999 17:30:47 +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 CC: Peter Garner , PostgreSQL Interfaces List Subject: Re: [INTERFACES] Re: ResultSet.getDate References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > Not sure. The first thing I'm thinking of, is removing the datestyle > support, and having the driver set a datestyle to one (probably ISO) > during the connect. AFAIK, the ODBC driver uses a similar scheme? Yes, sorry, I'd forgotten that you don't already do this. The ODBC driver does force the date format to ISO. > If we still have problems, how about an internal datestyle for use by > interfaces only (like JDBC & ODBC)? Sure, though the ISO style is pretty well defined and parsable, so may be the best choice for an ASCII internal format. - Tom