The Oracle database fuzzy query statement is a result that is easy to ignore: the problem of empty records

The Oracle database fuzzy query statement is easy to ignore: the cause of the null record problem: the SQL statement is as follows: select count (*) from test; the result is 1390. select count (*) from test where bb not like '% disable %' result 393. in the actual browsing process, it is found that the result set is not disabled and there are certainly more than 393 records.
Process: 1. First, we suspect that the character set problem may be that the client character set does not match the server character set. After the preceding SQL statement is used on another machine, www.2cto.com returns the same result with similar replications. 2. I still suspect that it is a character set problem. I have not found the real cause of the problem, and almost went crazy. 3. I accidentally found that many bb fields are empty. After careful analysis, I found that bb not like '% disabled %' does not match null records, so I changed it to select count (*) from test where bb not like '% disabled %' or bb is null, 1356 is returned. Conclusion:
Fuzzy match is not often used, so it will lead to careless use, and eventually lead to human madness.
Author: noodle123