Received: from golem.jpl.nasa.gov (root@hectic-1.jpl.nasa.gov [128.149.68.203]) by hub.org (8.8.8/8.7.5) with ESMTP id JAA18658 for ; Thu, 30 Apr 1998 09:05:53 -0400 (EDT) Received: from alumni.caltech.edu (localhost [127.0.0.1]) by golem.jpl.nasa.gov (8.8.5/8.8.5) with ESMTP id NAA09053; Thu, 30 Apr 1998 13:08:18 GMT Sender: tgl@mythos.jpl.nasa.gov Message-ID: <354877C1.3203C5F3@alumni.caltech.edu> Date: Thu, 30 Apr 1998 13:08:17 +0000 From: "Thomas G. Lockhart" Organization: Caltech/JPL X-Mailer: Mozilla 4.03 [en] (X11; I; Linux 2.0.30 i686) MIME-Version: 1.0 To: "Jose' Soares Da Silva" CC: Tom Ivar Helbekkmo , Postgres Hackers List Subject: Re: [INTERFACES] Access'97 and ODBC References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > > > I vote for changing default date format to ISO-8601 to reflect > > Hear! Hear! Good standards beat silly conventions any day! > Seems that you don't like conventions Tom, but you want > that all world use dates with American format. > Seems that you want impose one convention. > We're working with a database which name is PostgreSQL. > I suppose that you know what's mean the last 3 letters. Uh, Jose', he was agreeing with you :)) Anyway, imo the only issue is _when_ this kind of change should take place. My comment in the documentation did not promise that it would change in the next release, only that it might change in a future release. btw, I don't think that the ISO date style is mandated by the SQL92 standard, but it does seem like a good idea, particularly as we approach y2k... Of course, since we now have the PGDATESTYLE environment variable, usable by both the backend (at startup) and libpq (at connect time), perhaps a change in default date format is not something to worry about too much. I haven't heard any negative comments (yet) about changing the default date format to ISO-8601 (yyyy-mm-dd). Does anyone have a strong feeling that this should _not_ happen for v6.4?? Speak up or it might happen ;) - Tom