Unexpected ANTI JOIN Result

[TheoristCoder]

Dear Dolt Developers,
I encountered an unexpected execution result in Dolt and would greatly appreciate it if you could take a look. Let's make concerted efforts in enhancing the robustness of Dolt. Thank you very much!

CREATE TABLE t0(c0 BOOLEAN, PRIMARY KEY(c0));
INSERT INTO t0(c0) VALUES (false);

SELECT * FROM t0 WHERE NOT EXISTS (SELECT 1 FROM (SELECT 1) AS sub0 WHERE LOG2(t0.c0));
-- Wrong Execution Result: Empty result
-- Expected Result: 0

Commit: 8c2a083
Expected Results: https://www.db-fiddle.com/f/txeb7Fu8FitsCR5wkZgoKo/0

[angelamayxie]

This is likely due to LogBase.IsNullable() not returning true

[TheoristCoder]

Dear developers @angelamayxie , I want to kindly ask that if join hints support join with subquery? if the right table of the join is a subquery, can join hints be effective? Or do you have some detailed usage of join hint?

[timsehn]

We do support join hints: https://docs.dolthub.com/sql-reference/sql-support/miscellaneous#join-hints

[TheoristCoder]

We do support join hints: https://docs.dolthub.com/sql-reference/sql-support/miscellaneous#join-hints

Thank, but I really want know if join hint support to hint the join algorithm for join with subqueries? Is it only for single-tables?

[angelamayxie]

I believe subqueries are treated like tables in a join so join hints should still work.

Can you provide an example query of what you mean?

[TheoristCoder]

I believe subqueries are treated like tables in a join so join hints should still work.

Can you provide an example query of what you mean?

Like

select * from A Join (select c as col from B) as sub ON A.a = sub.col 

Can join hint control the join algorithms?