|11:52||• Ticket [c51489c3] Incorrect result from WITH RECURSIVE using DISTINCT status still Fixed with 3 other changes (artifact: 465c6275 user: drh)|
|00:47||• Fixed ticket [c51489c3]. (artifact: bc9cfc49 user: drh)|
|00:46||DISTINCT may not be ignored inside a UNION ALL common table expression. Fix for ticket [c51489c3b8f919c5] (check-in: 7d2b590d user: drh tags: trunk)|
|00:00||• New ticket [c51489c3] Incorrect result from WITH RECURSIVE using DEFAULT. (artifact: bc476067 user: drh)|
|Title:||Incorrect result from WITH RECURSIVE using DISTINCT|
|Last Modified:||2020-09-29 11:52:53|
|Version Found In:|
drh added on 2020-09-17 00:00:16:
The above should return 6 rows, but is returning 9 rows with all recent versions of SQLite. That 6 rows are correct is confirmed on sqlfiddle.com using PostgreSQL and SQL Server.
Bisect shows the problem first appeared in check-in 45d8cc678d128f1d on 2014-03-21 (6.5 years ago!) and was first released with version 3.8.5. The problem has not been reported from the field in all that time, which tells us that it is not a high priority to fix.
Problem reported on the Forum via post 1d3b0519e2.