Open GoogleCodeExporter opened 9 years ago
Original comment by ildar.absalyamov
on 12 Nov 2014 at 11:13
Two thoughts:
1. This is probably not our biggest bug - in fact it's not a bug, it's a
feature request. Just curious why it got filed?
2. Someone needs to think carefully about nulls to make sure it's really
redundant. (I'm not entirely convinced that such a predicate can be correctly
removed, but maybe so...)
Original comment by dtab...@gmail.com
on 13 Nov 2014 at 6:09
1. I was not claiming that's a bug, that's why it was filed as an Enhancement.
:-)
The reason this was brought up by issue 576. It was not clear to me why there
should be an R-tree lookup at all.
2. I agree in case of the nullable attributes predicate might not be evaluated
to True, but what is the case when $x.id!=$x.id?
Original comment by ildar.absalyamov
on 13 Nov 2014 at 6:52
I see that categorization now; cool.
Give it a try, but I suspect both the = and != cases will evaluate to unknown
rather than true or false, if I remember right. (In the final where-based
output, only the true survive in the end - the false and the unknown are
filtered.)
Original comment by dtab...@gmail.com
on 13 Nov 2014 at 6:59
OK, general case might not work in this case. What if there is an explicit not
null check?
Original comment by ildar.absalyamov
on 13 Nov 2014 at 7:32
Original issue reported on code.google.com by
ildar.absalyamov
on 12 Nov 2014 at 11:13