You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cayenne.apache.org by "Andrus Adamchik (JIRA)" <ji...@apache.org> on 2014/09/30 12:44:34 UTC

[jira] [Commented] (CAY-1957) Multiple inExp are grouped into one in()

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

Andrus Adamchik commented on CAY-1957:
--------------------------------------

What version of Cayenne is this? I can't reproduce this behavior with HEAD build of 3.2, which generates 

A in (...) AND A in (..)



> Multiple inExp are grouped into one in()
> ----------------------------------------
>
>                 Key: CAY-1957
>                 URL: https://issues.apache.org/jira/browse/CAY-1957
>             Project: Cayenne
>          Issue Type: Bug
>            Reporter: Graham Collinson
>            Priority: Minor
>
> If I were to write in sql
> Select * from test where a in (1,2,3) and a in (1,2)
>  
> I’d only get rows where a is 1 or 2.
>  
> If you do similar with cayenne expressions
>  
> Expression exp = ExpressionFactory.inExp(COLUMN_A, {set with 1,2,3})
> .andExp(ExpressionFactory.inExp(COLUMN_A, {set with 1,2});
>  
> Then cayenne will turn that into a sql statement like
> Select * from test where a in (1,2,3);
> Is this expected behaviour?
> To work more like SQL it would be better if there were 2 in statements or if it could be optimised to be in (1,2)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)