From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Docs: improve descriptions of ISO week-numbering date features. |
Date: | 2014-12-31 21:43:10 |
Message-ID: | E1Y6R2s-0002Px-1U@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Docs: improve descriptions of ISO week-numbering date features.
Use the phraseology "ISO 8601 week-numbering year" in place of just
"ISO year", and make related adjustments to other terminology.
The point of this change is that it seems some people see "ISO year"
and think "standard year", whereupon they're surprised when constructs
like to_char(..., "IYYY-MM-DD") produce nonsensical results. Perhaps
hanging a few more adjectives on it will discourage them from jumping
to false conclusions. I put in an explicit warning against that
specific usage, too, though the main point is to discourage people
who haven't read this far down the page.
In passing fix some nearby markup and terminology inconsistencies.
Branch
------
REL9_1_STABLE
Details
-------
http://git.postgresql.org/pg/commitdiff/ef207083c59edbbf11e1fcaf8d87b7c48cf1c2c1
Modified Files
--------------
doc/src/sgml/func.sgml | 87 +++++++++++++++++++++++++++++-------------------
1 file changed, 52 insertions(+), 35 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-12-31 22:04:31 | pgsql: Don't run rowsecurity in parallel with other regression tests. |
Previous Message | Tom Lane | 2014-12-31 19:45:15 | pgsql: Print more information about getObjectIdentityParts() failures. |