Re: A minor bug in the doc of "SQL Functions Returning Sets" in xfunc.sgml. - Mailing list pgsql-docs

From 日向充
Subject Re: A minor bug in the doc of "SQL Functions Returning Sets" in xfunc.sgml.
Date
Msg-id CAF-2iM8NcSDA9A0xwfYDuJH8H5DPkwDBsPp4ArwQWirq-eHthw@mail.gmail.com
Whole thread Raw
In response to Re: A minor bug in the doc of "SQL Functions Returning Sets" in xfunc.sgml.  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-docs
On Thu, Jul 18, 2024 at 9:05 PM Tom Lane
<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> "David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> > On Thu, Jul 18, 2024 at 7:10 PM Michael Paquier <michael(at)paquier(dot)xyz>
> wrote:
> >> Not sure that this is worth changing.  The examples work OK when taken
> >> in isolation or are able to demonstrate the point they want to show.
> >> In short, not all these queries are here to be compatible with the
> >> contents in the same area.  See for example the case of the "nodes"
> >> table on the same page, created nowhere.  "tab" is just a more generic
> >> table name that's more spread.
>
> > Clearly this page repeatedly expects tab.x to exist; and for these
> queries
> > to be executable.  This seems like the least invasive way to make that
> > expectation reality.
>
> I'm with Michael here.  Only in the tutorial do we expect there to be
> a continuing thread of commands that you can just copy-and-paste and
> expect to work.  I do not think it's reasonable to extend that policy
> to the rest of the manual: in other places, there are too many
> distinct topics under consideration and too much reason to make
> localized changes.
>

Thank you Michael, David and Tom Lane for your replies.
I understand the policy in this document.

Mitsuru Hinata
NTT Open Source Software Center

2024年7月19日(金) 13:15 David G. Johnston <david.g.johnston@gmail.com>:
>
> On Thu, Jul 18, 2024 at 9:05 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>
>> "David G. Johnston" <david.g.johnston@gmail.com> writes:
>> > On Thu, Jul 18, 2024 at 7:10 PM Michael Paquier <michael@paquier.xyz> wrote:
>> >> Not sure that this is worth changing.  The examples work OK when taken
>> >> in isolation or are able to demonstrate the point they want to show.
>> >> In short, not all these queries are here to be compatible with the
>> >> contents in the same area.  See for example the case of the "nodes"
>> >> table on the same page, created nowhere.  "tab" is just a more generic
>> >> table name that's more spread.
>>
>> > Clearly this page repeatedly expects tab.x to exist; and for these queries
>> > to be executable.  This seems like the least invasive way to make that
>> > expectation reality.
>>
>> I'm with Michael here.  Only in the tutorial do we expect there to be
>> a continuing thread of commands that you can just copy-and-paste and
>> expect to work.  I do not think it's reasonable to extend that policy
>> to the rest of the manual: in other places, there are too many
>> distinct topics under consideration and too much reason to make
>> localized changes.
>>
>
> So much for leaving a place a little nicer when you leave than when you arrived...
>
> David J.
>



pgsql-docs by date:

Previous
From: shveta malik
Date:
Subject: Re: Correction in doc of failover ready steps
Next
From: PG Doc comments form
Date:
Subject: Undocumented := alternative in using option of raise statement