[MDEV-13230] Information about EXCEPT ALL is inconsistent between KB, JIRA, code and tests Created: 2017-07-01  Updated: 2017-07-02  Resolved: 2017-07-02

Status: Closed
Project: MariaDB Server
Component/s: Documentation, Parser
Affects Version/s: 10.3
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: Elena Stepanova Assignee: Oleksandr Byelkin
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-10140 Add support for EXCEPT Closed

 Description   

It is unclear from the available sources whether EXCEPT ALL is supposed to work at all, and if it is, to what extent.

The KB says that is is not supported:

ALL is not supported by EXCEPT (and it is difficult to make sense of ALL with EXCEPT).

MDEV-10140 in scope of which EXCEPT was implemented says that ALL is supported, and explains the semantics (however strange it is):

With ALL, a row that has m duplicates in the left table and n duplicates in the right table will appear max(m-n,0) times in the result set.

Also, when EXCEPT ALL is executed in current pre-10.3.1 server, it throws an error, but it's not "unsupported":

MariaDB [test]> select * from t1 except all select * from t2;
ERROR 1221 (HY000): Incorrect usage of EXCEPT and ALL

So,

  • if EXCEPT ALL is not supported, I think it's better to throw the corresponding error message rather than Incorrect usage;
  • please reconcile KB with JIRA so they both contain correct information.


 Comments   
Comment by Oleksandr Byelkin [ 2017-07-02 ]

Inconsistemt is only MDEW (IMHO)

Comment by Oleksandr Byelkin [ 2017-07-02 ]

MDEV fixed

Generated at Thu Feb 08 08:03:56 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.