| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> |
| Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Adding an explaining title to Notes on SGML |
| Date: | 2026-04-23 12:27:08 |
| Message-ID: | CAKFQuwaDcsiaiBF5eJAM5EPD4TQ3rKV93duvyXV-RprYcp+25w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thursday, April 23, 2026, Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> wrote:
> Em qui., 23 de abr. de 2026 às 04:55, Daniel Gustafsson <daniel(at)yesql(dot)se>
> escreveu:
>
>> Wouldn't it make more sense to refactor to move the information in the
>> note
>> closer to what the note is regarding?
>
>
> Also, a note refers to two items in the table, which are bool_and and
> bool_or, so what do we do ? Repeat the information ?
>
Personally, I’d like to do two things here instead of a note. Use a
footnote, but add entries for any/some to the table and use the description
to say they are not implemented and to use bool_and/bool_or instead, then
anchor the footnote at these entries.
That way, people looking for these SQL standard functions actually find
them where they expect and understand why they are missing. Index entries
wouldn’t hurt.
The note actually seems counter-productive for the typical PostgreSQL user
who doesn’t even know what is in the standard. And an unintuitive place to
look if you know the function names already.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | SCHOEMANS Maxime | 2026-04-23 12:32:13 | Re: Implement missing join selectivity estimation for range types |
| Previous Message | Marcos Pegoraro | 2026-04-23 12:13:50 | Re: Adding an explaining title to Notes on SGML |