Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Y5fYo-0002LS-7d for pgsql-docs@arkaria.postgresql.org; Mon, 29 Dec 2014 19:00:58 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Y5fYn-0006w8-LB for pgsql-docs@arkaria.postgresql.org; Mon, 29 Dec 2014 19:00:57 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1Y5fYm-0006uB-Rl for pgsql-docs@postgresql.org; Mon, 29 Dec 2014 19:00:57 +0000 Received: from mwork.nabble.com ([162.253.133.43]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Y5fYj-0004QC-KV for pgsql-docs@postgresql.org; Mon, 29 Dec 2014 19:00:55 +0000 Received: from msam.nabble.com (unknown [162.253.133.85]) by mwork.nabble.com (Postfix) with ESMTP id 47C99EFF755 for ; Mon, 29 Dec 2014 11:00:53 -0800 (PST) Date: Mon, 29 Dec 2014 12:00:52 -0700 (MST) From: David G Johnston To: pgsql-docs@postgresql.org Message-ID: <1419879652755-5832322.post@n5.nabble.com> In-Reply-To: <5888.1419865569@sss.pgh.pa.us> References: <5888.1419865569@sss.pgh.pa.us> Subject: Re: The IYYY mess again MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -0.3 (/) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org Tom Lane-2 wrote > In bug #12367 > http://www.postgresql.org/message-id/ > 20141229031218.8013.51171@.postgresql > > There is a warning against combining IYYY with MM/DD, but it's buried > in trivia far down the page. Can we move this warning/notice into code? Basically warn/disallow IYYY-MM-DD (and similar) as a valid format? And why not make it an error. If someone really needed to output mixed modes they would be able to concatenate the two halves together to get the desired result so it isn't like we are making it impossible to accomplish - but the typical mistake goes away. David J. -- View this message in context: http://postgresql.nabble.com/The-IYYY-mess-again-tp5832272p5832322.html Sent from the PostgreSQL - docs mailing list archive at Nabble.com. -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs