[
https://issues.apache.org/jira/browse/TORQUE-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17713596#comment-17713596
]
Georg Kallidis commented on TORQUE-363:
---------------------------------------
yes, that's it IMO! I encourage you to add this new constructor and may be a
check in CriterionTest#testIsNullInCriterion or another test.
> Criterion handles "IS NULL" incorrectly
> ---------------------------------------
>
> Key: TORQUE-363
> URL: https://issues.apache.org/jira/browse/TORQUE-363
> Project: Torque
> Issue Type: Bug
> Components: Runtime
> Affects Versions: 5.0, 5.1
> Reporter: Max Philipp Wriedt
> Assignee: Max Philipp Wriedt
> Priority: Major
> Labels: criteria_api, criterion
>
> When using Criterion and want to use ISNULL (and maybe also applicable to
> ISNOTNULL)
> {code:java}
> Criterion criterion1 = new Criterion(ID, Criteria.ISNULL); {code}
> The generated Code adds an equal-sign (=). In a Criteria this is not the case.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscr...@db.apache.org
For additional commands, e-mail: torque-dev-h...@db.apache.org
