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

Jessie updated OAK-3561:
------------------------
    Description: 
When working with Oak 1.2.7, I find the following query shows 0 result 
(Jackrabbit 2.10 outputs the correct rows).

"SELECT case.[jcr:uuid] as uuid FROM [xx.Patient] as patient INNER JOIN 
[xx:Case] as case ON patient.[jcr:uuid] = case.[patient] WHERE patient.[name] 
LIKE 'someone%'

case.[patient] is defined as weakreference type, representing patient

I just wonder whether it is a bug or such query should be expressed in another 
way in OAK?

Thank you very much!

  was:
When working with Oak 1.2.7, I find the following query shows 0 result 
(Jackrabbit 2.10 outputs the correct rows).

"SELECT case.[jcr:uuid] as uuid FROM [xx.Patient] as patient INNER JOIN 
[xx:Case] as case ON patient.[jcr:uuid] = case.[patient] WHERE patient.[name] = 
'someone%'

case.[patient] is defined as weakreference type, representing patient

I just wonder whether it is a bug or such query should be expressed in another 
way in OAK?

Thank you very much!


> Query Constraints of "reference" property
> -----------------------------------------
>
>                 Key: OAK-3561
>                 URL: https://issues.apache.org/jira/browse/OAK-3561
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: query
>    Affects Versions: 1.2.7
>         Environment: Java 1.8.0_11 with Mongodb 3.0.6 on Windows 7
>            Reporter: Jessie
>
> When working with Oak 1.2.7, I find the following query shows 0 result 
> (Jackrabbit 2.10 outputs the correct rows).
> "SELECT case.[jcr:uuid] as uuid FROM [xx.Patient] as patient INNER JOIN 
> [xx:Case] as case ON patient.[jcr:uuid] = case.[patient] WHERE patient.[name] 
> LIKE 'someone%'
> case.[patient] is defined as weakreference type, representing patient
> I just wonder whether it is a bug or such query should be expressed in 
> another way in OAK?
> Thank you very much!



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

Reply via email to