From: Steve Atkins <steve@blighty.com>
To: pgsql-docs@postgreSQL.org
Subject: Re: The IYYY mess again
Date: Mon, 29 Dec 2014 09:13:33 -0800
Message-ID: <59DE6D33-8AE5-4355-BC1D-4911CD2EAD34@blighty.com> (raw)
In-Reply-To: <5888.1419865569@sss.pgh.pa.us>
References: <5888.1419865569@sss.pgh.pa.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-docs>
On Dec 29, 2014, at 7:06 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> In bug #12367
> http://www.postgresql.org/message-id/20141229031218.8013.51171@wrigleys.postgresql.org
> we see yet another iteration of somebody trying to combine to_char's
> IYYY specifier with regular Gregorian MM/DD fields.
>
> It occurs to me that this is largely our own fault, because the fine
> manual just defines IYYY as "ISO year". I'm sure the typical newbie
> thought process is "that sounds like a standard year, I'll use that".
> There is a warning against combining IYYY with MM/DD, but it's buried
> in trivia far down the page.
>
> I did a bit of googling and came across
> http://en.wikipedia.org/wiki/ISO_week_date
> in which this construct is called an "ISO week-numbering year".
>
> Not having a copy of ISO 8601, I'm not sure if that's the standard's
> terminology; but ISTM that if we consistently referred to the Ixxx
> format specifiers as "ISO week-numbering foo" then this type of error
> might become a little less attractive.
>
> Objections, better ideas?
I've seen this problem a few times on IRC too. An explicit warning / cross
reference on IYYY that the user almost certainly wants YYYY instead might
be even better.
Cheers,
Steve
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: steve@blighty.com
Subject: Re: The IYYY mess again
In-Reply-To: <59DE6D33-8AE5-4355-BC1D-4911CD2EAD34@blighty.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox