Re: incorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual
On 23.02.24 12:23, 小泉 悟 wrote: Upon closer inspection, F305 is also "INTERSECT ALL table operator”. Perhaps F302-02 would be unnecessary. Correct, F302-02 should have been deleted. I have fixed it, thanks. 2024/02/23 18:06、Daniel Gustafsson のメール: On 23 Feb 2024, at 06:36, PG Doc comments form 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
Re: incorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual
> On 23 Feb 2024, at 12:23, 小泉 悟 wrote: > Upon closer inspection, F305 is also "INTERSECT ALL table operator”. > Perhaps F302-02 would be unnecessary. The list is intended to reflect what's in the SQL:2023 standard, so whatever the standard says we should too. I don't have a copy of the standard though so I'll leave it to someone who does comment. -- Daniel Gustafsson
Re: incorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual
Upon closer inspection, F305 is also "INTERSECT ALL table operator”. Perhaps F302-02 would be unnecessary. > 2024/02/23 18:06、Daniel Gustafsson のメール: > >> On 23 Feb 2024, at 06:36, PG Doc comments form >> 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 > >
Re: incorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual
> On 23 Feb 2024, at 06:36, PG Doc comments form 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 Description: Binary data
incorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/16/features-sql-standard.html Description: In "D.1. Supported Features"(https://www.postgresql.org/docs/current/features-sql-standard.html), identifiers appear as following: F302INTERSECT table operator F303INTERSECT DISTINCT table operator F302-02 INTERSECT ALL table operator F304EXCEPT ALL table operator The correct result would be as follows: F302INTERSECT table operator F302-02 INTERSECT ALL table operator F303INTERSECT DISTINCT table operator F304EXCEPT ALL table operator
