Received: from mail.postgresql.org (webmail.postgresql.org [216.126.85.28]) by mail.postgresql.org (8.11.1/8.11.1) with SMTP id f16D8hx74680 for ; Tue, 6 Feb 2001 08:08:43 -0500 (EST) (envelope-from pgsql-sql-owner@postgresql.org) Received: from rah.vcsn.com ([207.113.7.1]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f15HGTx36850 for ; Mon, 5 Feb 2001 12:16:29 -0500 (EST) (envelope-from keith@vcsn.com) Received: from localhost (keith@localhost) by rah.vcsn.com (8.9.1a/8.9.1) with ESMTP id MAA16983; Mon, 5 Feb 2001 12:16:07 -0500 Date: Mon, 5 Feb 2001 12:16:07 -0500 (EST) From: To: Karel Zak cc: pgsql-sql@postgresql.org Subject: Re: Problem with Day of Week In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200102/77 X-Sequence-Number: 1256 Always- I think I'll use the to_char since I think you all are saying that that is ISO or at least POSIX. On Mon, 5 Feb 2001, Karel Zak wrote: > > On Mon, 5 Feb 2001 keith@vcsn.com wrote: > > > Ok, so there is actually two standards then. Is this documented > > anywhere? Is this is something that is going to change? I don't want > > to write and app and have things "break" during and upgrade :) > > I mean you can be caseful. Not changes planned here. > > date_part() is not documented to much in detail, but formatting > functions are described good. > > Karel >