raghavyadav01 commented on issue #5492:
URL: https://github.com/apache/datafusion/issues/5492#issuecomment-6485710291

   @alamb how can I help with this? Happy to take whatever is most useful.
   
   Here is the latest run report: every repro in the list above, rerun on main 
(8733e2edc) and checked against DuckDB 1.5.6.
   
   Fixed on main, so these can be ticked or closed:
   - #25024 now returns `z`
   - #25480 now returns `2, 4, NULL`
   - #25347 all 8 shapes match, including the six constant-value ones from 
https://github.com/apache/datafusion/issues/25347#issuecomment-5689471249
   - #24960 the `EXISTS` and `NOT EXISTS` repros are correct. The one shape 
still wrong (`HAVING count(*) + t1.t1_int > 1`) is already covered by #26695
   - #16134 and #17349 were closed today
   
   Now an error instead of a wrong result, so it can move to the second list:
   - #26508 fails with `Physical plan does not support logical expression 
ScalarSubquery`
   
   Listed as unsupported, but it actually returns wrong results:
   - #21198. An inner `LATERAL` with `HAVING` is planned as a right join, so 
outer rows that fail the `HAVING` come back with `NULL` instead of being 
dropped:
   
   ```sql
   CREATE TABLE a(k INT) AS VALUES (1), (2), (3);
   CREATE TABLE b(k INT, v INT) AS VALUES (1, 10), (1, 20), (2, 30);
   SELECT a.k, s.c FROM a, LATERAL (SELECT count(*) AS c FROM b WHERE b.k = a.k 
HAVING count(*) > 1) s;
   -- main: (1, 2), (2, NULL), (3, NULL)
   -- DuckDB: (1, 2)
   ```
   
   Still wrong as described: #26695, #26692, #26629, #26505, #26503, #26234, 
#26032, #26014, #25808, and #26569 (from the code: the value key count still 
defaults to 1). The #26234 repro uses `outer` as a table alias, which no longer 
parses, but with the alias renamed it is still wrong.
   
   Every query in the unsupported list still fails to plan.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to