[jira] [Commented] (TORQUE-363) Criterion handles "IS NULL" incorrectly

["Max Philipp Wriedt (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TORQUE-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17712644#comment-17712644 ] 

Max Philipp Wriedt commented on TORQUE-363:
-------------------------------------------

We could handle a Criterion constructed with SqlEnum as second value:

 
{code:java}
public Criterion(final Object lValue, final SqlEnum sqlEnum)
{
    this(lValue, null, sqlEnum, null, null);
} {code}
or do I overlook something?

 

> 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
>            Priority: Critical
>              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-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org