Re: The IYYY mess again

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-docs(at)postgreSQL(dot)org
Subject: Re: The IYYY mess again
Date: 2014-12-29 22:41:30
Message-ID: 20141229224130.GC5788@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Mon, Dec 29, 2014 at 10:06:09AM -0500, Tom Lane 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?

+1 for saying "ISO week-numbering year".

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ Everyone has their own god. +

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Bruce Momjian 2015-01-06 17:59:01 Re: [DOCS] suggestion about SEO on www.postgresql.org/docs
Previous Message David Johnston 2014-12-29 19:25:34 Re: The IYYY mess again