None-value problems that arose about minidb HOT 2 CLOSED

Hello,
That's correct, the 3rd issue was resolved easily with the addition you suggested. However the second issue (INLJ) still fails, so some debugging and fixing is needed (I will have it completed in a few days time). It probably happens because it tries to compare the None values of a table with the values of the index.

Apart from that, I will try to troubleshoot and find the reason behind the 5th issue's failure.

To summarize: 1 and 3 are completed, I will look into 2 and 5 and, finally, I will wait for you to decide how the 4th issue should be approached.

I think that's all for now :)

from minidb.

Hey,

No. 3 can be easily solved by adding this to line 666. I missed it somehow. That should take care of 1-3.
if key is None: continue

No. 4 is true and solving is without using a "hacky" way is not trivial. I will look into it.

No. 5 is not true for the master version. Maybe you should try to find out what was added that caused this bug

from minidb.