On Dec 9, 2011, at 11:54 , Lukas Kahwe Smith wrote:
> Hi,
>
> I am wondering if this is a bug or a feature.
>
> I have a query with a join. notice the SELECT data.*
>
> SELECT
> data.*
> FROM
> [nzz:unstructured] AS data
> LEFT OUTER JOIN [nzz:unstructured] AS referring ON referring.reference =
> data.[jcr:uuid]
> WHERE
> (referring.reference IS NOT NULL AND ISDESCENDANTNODE(referring,
> '/article/2011/12/08'))
> OR
> ISDESCENDANTNODE(data, '/article/2011/12/08')
>
>
> But I actually end up with rows like the following, aka 'referring' is still
> listed.
ok via davex I get
<D:multistatus xmlns:D="DAV:">
<D:response>
<D:href>http://localhost:8080/server/foo/jcr%3aroot/article/2011/12/08/N_J4252/</D:href>
<D:propstat>
<D:prop>
<dcr:search-result-property
xmlns:dcr="http://www.day.com/jcr/webdav/1.0";>
<dcr:column>
<dcr:name>data.jcr:primaryType</dcr:name>
<dcr:value dcr:type="Name">nt:unstructured</dcr:value>
</dcr:column>
<dcr:column>
<dcr:name>jcr:path</dcr:name>
<dcr:value dcr:type="Path">/article/2011/12/08/N_J4252</dcr:value>
<dcr:selectorName>data</dcr:selectorName>
</dcr:column>
<dcr:column>
<dcr:name>jcr:score</dcr:name>
<dcr:value dcr:type="Double">6.761604309082031</dcr:value>
<dcr:selectorName>data</dcr:selectorName>
</dcr:column>
<dcr:column>
<dcr:name>jcr:path</dcr:name>
<dcr:selectorName>referring</dcr:selectorName>
</dcr:column>
<dcr:column>
<dcr:name>jcr:score</dcr:name>
<dcr:value dcr:type="Double">0.0</dcr:value>
<dcr:selectorName>referring</dcr:selectorName>
</dcr:column>
</dcr:search-result-property>
</D:prop>
<D:status>HTTP/1.1 200 OK</D:status>
</D:propstat>
</D:response>
Does anyone have a hint how this is handled inside the Java JCR API?
Is there some iterator that lets you filter by selector or is this something
the user has to implement himself?
regards,
Lukas Kahwe Smith
[email protected]
