[jira] [Resolved] (RAVE-105) PersonServiceDb: call addFilterClause with 'special' property adds nothing

["Matt Franklin (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/RAVE-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Franklin resolved RAVE-105.
--------------------------------

       Resolution: Won't Fix
    Fix Version/s: 0.3-INCUBATING

Replacing person service implementation

> PersonServiceDb: call addFilterClause with 'special' property adds nothing
> --------------------------------------------------------------------------
>
>                 Key: RAVE-105
>                 URL: https://issues.apache.org/jira/browse/RAVE-105
>             Project: Rave
>          Issue Type: Bug
>    Affects Versions: 0.1-INCUBATING
>            Reporter: Jasha Joachimsthal
>             Fix For: 0.3-INCUBATING
>
>
> While writing the unit test for PersonServiceDb#addFilterClause I found out that 
> if (FilterSpecification.isSpecial(filter)) 
> is true then none of the subclauses can be met (because they try to compare different String's to the same variable.
> It then returns 0 as position which means the filter clause will not be added.
> Is this intentional or is it a bug?
> See also PersonServiceDbTest#testAddSpecialFilterClause

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira