| From: | 小泉 悟 <koizumistr(at)minos(dot)ocn(dot)ne(dot)jp> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | pgsql-docs <pgsql-docs(at)lists(dot)postgresql(dot)org>, Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Subject: | Re: incorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual |
| Date: | 2024-02-23 11:23:57 |
| Message-ID: | B14F0BC8-42A2-4779-94ED-F7624A11C3B1@minos.ocn.ne.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Upon closer inspection, F305 is also "INTERSECT ALL table operator”.
Perhaps F302-02 would be unnecessary.
> 2024/02/23 18:06、Daniel Gustafsson <daniel(at)yesql(dot)se>のメール:
>
>> On 23 Feb 2024, at 06:36, PG Doc comments form <noreply(at)postgresql(dot)org> wrote:
>
>> The correct result would be as follows:
>>
>> F302 INTERSECT table operator
>> F302-02 INTERSECT ALL table operator
>> F303 INTERSECT DISTINCT table operator
>> F304 EXCEPT ALL table operator
>
> This was changed recently in c9f57541d970 which changed subfeatures to
> top-level features to match the SQL:2023 standard, F303 was previously a
> sub-feature named F302-01. That being said, I agree that it makes sense to
> place F303 below F302-02 as per the attached, unless Peter (on cc:) objects.
>
> --
> Daniel Gustafsson
>
> <f303.diff>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2024-02-23 12:27:14 | Re: incorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual |
| Previous Message | Daniel Gustafsson | 2024-02-23 09:06:54 | Re: incorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual |