Do more optimization when do comparison with null values
Open
sig/planner
type/enhancement
- Dominant language
- Go
- Stars
- 40.5k
- Forks
- 6.2k
- PR merge metrics
- PR metrics pending
Description
## Enhancement
Currently, TiDB only do optimization when doing equal comparsion with null values(such as `where a = null`), while when it comes to other comparsion(including >= | <= | != | > | < ) with null values, TiDB not do related optimization.
Considering everything compared with null is always null, we can do more optimization in these cases.
Contributor guide
Assessment
This issue has not been assessed yet.