[
https://issues.apache.org/jira/browse/OFBIZ-4393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148121#comment-13148121
]
Anne Jessel commented on OFBIZ-4393:
------------------------------------
On consideration, I don't think the change in behaviour is a major problem.
This patch supports EQUALS with null, which the previous code did not support.
IMO comparisons with null are very useful. However we lose the specific
NOT_EQUAL with empty string, IMO an uncommon test, especially in a view-entity.
Overall a big gain, but perhaps not yet a perfect solution.
> View entity condition-expr doesn't handle null
> ----------------------------------------------
>
> Key: OFBIZ-4393
> URL: https://issues.apache.org/jira/browse/OFBIZ-4393
> Project: OFBiz
> Issue Type: Bug
> Components: framework
> Affects Versions: SVN trunk
> Environment: Rev 1165137
> Reporter: Anne Jessel
> Assignee: Adrian Crum
> Attachments: OFBIZ-4393-view-entity_condition-expr_null.patch,
> OFBIZ-4393-view-entity_condition-expr_null.patch,
> OFBIZ-4393-view-entity_condition-expr_null.patch
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> condition-expr tag in view-entity can't be used to compare a field with null.
> An absent value attribute is read as an empty string, and the code currently
> checks for value being null to know when to compare against null.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
