Red Hat Bugzilla – Bug 1256732
Guided DT, Analysis: issues with 'is null' and 'is not null' operators not detected correctly
Last modified: 2016-07-31 21:21:09 EDT
Description of problem:
A rule/row with 'Fact( fieldInt != null , fieldInt == 0 )' will give an 'Impossible match' warning.
A rule/row with 'Fact( fieldInt == 0 )' will also give an 'Impossible match' warning, if the cell for 'fieldInt != null' column is unchecked.
The two cases above are okay for String type fields (Integer/numerical type fields are affected).
A rule/row with 'Fact( fieldString == null , fieldString == "sth" )' should result in an 'Impossible match' warning, but doesn't.
The case above is okay for an Integer type field (String type fields are affected).
A rule/row with 'Fact( field != null )' or 'Fact( field == null )' and some action will give a 'Rule has no restrictions and will always fire' warning.
Version-Release number of selected component (if applicable):