Bug 1256732 - Guided DT, Analysis: issues with 'is null' and 'is not null' operators not detected correctly
Guided DT, Analysis: issues with 'is null' and 'is not null' operators not de...
Status: NEW
Product: JBoss BRMS Platform 6
Classification: JBoss
Component: Business Central (Show other bugs)
6.2.0
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Toni Rikkola
Lukáš Petrovický
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-08-25 06:56 EDT by Zuzana Krejčová
Modified: 2016-07-31 21:21 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Zuzana Krejčová 2015-08-25 06:56:48 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):
6.2 ER1

Note You need to log in before you can comment on or make changes to this bug.