| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Navrátil, Ondřej <onavratil(at)monetplus(dot)cz> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Peter Eisentraut <peter(at)eisentraut(dot)org>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: COALESCE documentation |
| Date: | 2024-07-03 12:34:57 |
| Message-ID: | CAKFQuwbn+rCSOtniW8aa6DCPeC-q6kYj8d2aCt6e8v56tC4kNQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Wednesday, July 3, 2024, Navrátil, Ondřej <onavratil(at)monetplus(dot)cz> wrote:
>
> To get back to my "docs patch proposal" - I could submit a patch if you
> would kindly point me where to start. I would also prefer to submit such a
> patch only after it is decided whether this is a docs bug or impl bug, and
> whether or not it will be fixed (it would be suitable to put a disclaimer
> in case the implementation intentionally diverges from the standard). Most
> importantly, the implementation and documentation should be in accord, even
> if it means both of them deviate from the standard.
>
I’m already writing a patch to better document NULL behavior in PostgreSQL
and will add whatever we come up with to that. I really doubt we are
going to change this in the name of standard conformance. One can get
standard behavior via case of really needed.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2024-07-03 14:41:19 | Re: COALESCE documentation |
| Previous Message | Peter Eisentraut | 2024-07-03 10:40:16 | Re: tutorial not accurate |