Details
-
Enhancement
-
Resolution: Unresolved
-
Major
-
None
-
8.36.0.Final
-
None
-
2023 Week 15-17 (from Apr 10), 2023 Week 18-20 (from May 1), 2023 Week 21-23 (from May 22), 2023 Week 27-29 (from Jul 3), 2023 Week 30-32 (from Jul 24), 2023 Week 33-35 (from Aug 14), 2023 Week 36-38 (from Sep 4), 2023 Week 24-26 (from Jun 12)
-
NEW
-
NEW
-
---
-
---
Description
Issue Description:
Users sometimes write a decision table which generates inefficient DRLs. A bind variable is declared in the previous column and the bind variable is used (only evaluating the variable, not Join) in the later column. Note that these columns are not combined, so result in different patterns.
We can move such a constraint to the right pattern. It would provide correct property reactivity
(before)
when
$fact1 : Fact1( $id1 : id == 1 )
Fact2( $id2 : id == 2 )
Fact2( id == 2, convertToIdString($id2) == "id2" )
then
(after)
when
$fact1 : Fact1( $id1 : id == 1 )
Fact2( $id2 : id == 2, convertToIdString($id2) == "id2" )
Fact2( id == 2 )
then
Acceptance Criteria:
- Implement the optimization. Enabled by default.
Attachments
Issue Links
- is related to
-
DROOLS-7398 executable model doesn't resolve bind variable from another pattern of the same type in method call in LHS for property reactivity
-
- Resolved
-