Bug 1256732 - Guided DT, Analysis: issues with 'is null' and 'is not null' operators not detected correctly
Summary: Guided DT, Analysis: issues with 'is null' and 'is not null' operators not de...
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Toni Rikkola
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-25 10:56 UTC by Zuzana Krejčová
Modified: 2020-03-27 19:34 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 19:34:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1263233 0 medium CLOSED Issues in guided dtable analysis - ConditionInspectors 2021-02-22 00:41:40 UTC

Internal Links: 1263233

Description Zuzana Krejčová 2015-08-25 10:56:48 UTC
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.