public inbox for [email protected]
help / color / mirror / Atom feedpgsql: Doc: improve explanation of type interval, especially extract().
5+ messages / 1 participants
[nested] [flat]
* pgsql: Doc: improve explanation of type interval, especially extract().
@ 2024-02-20 19:35 Tom Lane <[email protected]>
0 siblings, 0 replies; 5+ messages in thread
From: Tom Lane @ 2024-02-20 19:35 UTC (permalink / raw)
To: [email protected]
Doc: improve explanation of type interval, especially extract().
The explanation of interval's behavior in datatype.sgml wasn't wrong
exactly, but it was unclear, partly because it buried the lede about
there being three internal fields. Rearrange and wordsmith for more
clarity.
The discussion of extract() claimed that input of type date was
handled by casting, but actually there's been a separate SQL function
taking date for a very long time. Also, it was mostly silent about
how interval inputs are handled, but there are several field types
for which it seems useful to be specific.
Improve discussion of justify_days()/justify_hours() too.
In passing, remove vertical space in some groups of examples,
as there was little consistency about whether to have such space
or not. (I only did this within the datetime functions section;
there are some related inconsistencies elsewhere.)
Per discussion of bug #18348 from Michael Bondarenko. There
may be some code changes coming out of that discussion too,
but we likely won't back-patch them. This docs-only patch
seems useful to back-patch, though I only carried it back to
v13 because it didn't apply easily in v12.
Discussion: https://postgr.es/m/[email protected]
Branch
------
REL_16_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/3ad319b8cad497d0a130fe92a372e9177f9f7ee8
Modified Files
--------------
doc/src/sgml/datatype.sgml | 71 ++++++++++++++++-------------
doc/src/sgml/func.sgml | 109 +++++++++++++++++++++++----------------------
2 files changed, 96 insertions(+), 84 deletions(-)
^ permalink raw reply [nested|flat] 5+ messages in thread
* pgsql: Doc: improve explanation of type interval, especially extract().
@ 2024-02-20 19:35 Tom Lane <[email protected]>
0 siblings, 0 replies; 5+ messages in thread
From: Tom Lane @ 2024-02-20 19:35 UTC (permalink / raw)
To: [email protected]
Doc: improve explanation of type interval, especially extract().
The explanation of interval's behavior in datatype.sgml wasn't wrong
exactly, but it was unclear, partly because it buried the lede about
there being three internal fields. Rearrange and wordsmith for more
clarity.
The discussion of extract() claimed that input of type date was
handled by casting, but actually there's been a separate SQL function
taking date for a very long time. Also, it was mostly silent about
how interval inputs are handled, but there are several field types
for which it seems useful to be specific.
Improve discussion of justify_days()/justify_hours() too.
In passing, remove vertical space in some groups of examples,
as there was little consistency about whether to have such space
or not. (I only did this within the datetime functions section;
there are some related inconsistencies elsewhere.)
Per discussion of bug #18348 from Michael Bondarenko. There
may be some code changes coming out of that discussion too,
but we likely won't back-patch them. This docs-only patch
seems useful to back-patch, though I only carried it back to
v13 because it didn't apply easily in v12.
Discussion: https://postgr.es/m/[email protected]
Branch
------
REL_15_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/6d03e8109250c1d23aa10f8ae01b21469b0f8be2
Modified Files
--------------
doc/src/sgml/datatype.sgml | 71 ++++++++++++++++-------------
doc/src/sgml/func.sgml | 109 +++++++++++++++++++++++----------------------
2 files changed, 96 insertions(+), 84 deletions(-)
^ permalink raw reply [nested|flat] 5+ messages in thread
* pgsql: Doc: improve explanation of type interval, especially extract().
@ 2024-02-20 19:35 Tom Lane <[email protected]>
0 siblings, 0 replies; 5+ messages in thread
From: Tom Lane @ 2024-02-20 19:35 UTC (permalink / raw)
To: [email protected]
Doc: improve explanation of type interval, especially extract().
The explanation of interval's behavior in datatype.sgml wasn't wrong
exactly, but it was unclear, partly because it buried the lede about
there being three internal fields. Rearrange and wordsmith for more
clarity.
The discussion of extract() claimed that input of type date was
handled by casting, but actually there's been a separate SQL function
taking date for a very long time. Also, it was mostly silent about
how interval inputs are handled, but there are several field types
for which it seems useful to be specific.
Improve discussion of justify_days()/justify_hours() too.
In passing, remove vertical space in some groups of examples,
as there was little consistency about whether to have such space
or not. (I only did this within the datetime functions section;
there are some related inconsistencies elsewhere.)
Per discussion of bug #18348 from Michael Bondarenko. There
may be some code changes coming out of that discussion too,
but we likely won't back-patch them. This docs-only patch
seems useful to back-patch, though I only carried it back to
v13 because it didn't apply easily in v12.
Discussion: https://postgr.es/m/[email protected]
Branch
------
REL_13_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/eb1d008a7a18f2cf863e21e285b6db5858d0d5d9
Modified Files
--------------
doc/src/sgml/datatype.sgml | 71 ++++++++++++++++-------------
doc/src/sgml/func.sgml | 108 +++++++++++++++++++++++----------------------
2 files changed, 96 insertions(+), 83 deletions(-)
^ permalink raw reply [nested|flat] 5+ messages in thread
* pgsql: Doc: improve explanation of type interval, especially extract().
@ 2024-02-20 19:35 Tom Lane <[email protected]>
0 siblings, 0 replies; 5+ messages in thread
From: Tom Lane @ 2024-02-20 19:35 UTC (permalink / raw)
To: [email protected]
Doc: improve explanation of type interval, especially extract().
The explanation of interval's behavior in datatype.sgml wasn't wrong
exactly, but it was unclear, partly because it buried the lede about
there being three internal fields. Rearrange and wordsmith for more
clarity.
The discussion of extract() claimed that input of type date was
handled by casting, but actually there's been a separate SQL function
taking date for a very long time. Also, it was mostly silent about
how interval inputs are handled, but there are several field types
for which it seems useful to be specific.
Improve discussion of justify_days()/justify_hours() too.
In passing, remove vertical space in some groups of examples,
as there was little consistency about whether to have such space
or not. (I only did this within the datetime functions section;
there are some related inconsistencies elsewhere.)
Per discussion of bug #18348 from Michael Bondarenko. There
may be some code changes coming out of that discussion too,
but we likely won't back-patch them. This docs-only patch
seems useful to back-patch, though I only carried it back to
v13 because it didn't apply easily in v12.
Discussion: https://postgr.es/m/[email protected]
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/fcd210d496dad7d9f68c9399113368ccf2f009b9
Modified Files
--------------
doc/src/sgml/datatype.sgml | 71 +++++++++++++++++------------
doc/src/sgml/func.sgml | 111 ++++++++++++++++++++++-----------------------
2 files changed, 96 insertions(+), 86 deletions(-)
^ permalink raw reply [nested|flat] 5+ messages in thread
* pgsql: Doc: improve explanation of type interval, especially extract().
@ 2024-02-20 19:35 Tom Lane <[email protected]>
0 siblings, 0 replies; 5+ messages in thread
From: Tom Lane @ 2024-02-20 19:35 UTC (permalink / raw)
To: [email protected]
Doc: improve explanation of type interval, especially extract().
The explanation of interval's behavior in datatype.sgml wasn't wrong
exactly, but it was unclear, partly because it buried the lede about
there being three internal fields. Rearrange and wordsmith for more
clarity.
The discussion of extract() claimed that input of type date was
handled by casting, but actually there's been a separate SQL function
taking date for a very long time. Also, it was mostly silent about
how interval inputs are handled, but there are several field types
for which it seems useful to be specific.
Improve discussion of justify_days()/justify_hours() too.
In passing, remove vertical space in some groups of examples,
as there was little consistency about whether to have such space
or not. (I only did this within the datetime functions section;
there are some related inconsistencies elsewhere.)
Per discussion of bug #18348 from Michael Bondarenko. There
may be some code changes coming out of that discussion too,
but we likely won't back-patch them. This docs-only patch
seems useful to back-patch, though I only carried it back to
v13 because it didn't apply easily in v12.
Discussion: https://postgr.es/m/[email protected]
Branch
------
REL_14_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/ebf52e9b753250a0be07375c8c5f290e87edef2f
Modified Files
--------------
doc/src/sgml/datatype.sgml | 71 ++++++++++++++++-------------
doc/src/sgml/func.sgml | 109 +++++++++++++++++++++++----------------------
2 files changed, 96 insertions(+), 84 deletions(-)
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2024-02-20 19:35 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2024-02-20 19:35 pgsql: Doc: improve explanation of type interval, especially extract(). Tom Lane <[email protected]>
2024-02-20 19:35 pgsql: Doc: improve explanation of type interval, especially extract(). Tom Lane <[email protected]>
2024-02-20 19:35 pgsql: Doc: improve explanation of type interval, especially extract(). Tom Lane <[email protected]>
2024-02-20 19:35 pgsql: Doc: improve explanation of type interval, especially extract(). Tom Lane <[email protected]>
2024-02-20 19:35 pgsql: Doc: improve explanation of type interval, especially extract(). Tom Lane <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox