jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Klimetschek (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-2765) JCR-SQL2 : no count when WHERE clause is provided
Date Thu, 21 Oct 2010 18:52:19 GMT

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

Alexander Klimetschek updated JCR-2765:
---------------------------------------

      Priority: Major  (was: Blocker)
    Issue Type: Improvement  (was: Bug)

This is not a blocker - maybe for your requirements, but not for Jackrabbit. A blocker would
be that jackrabbit does not start, no nodes/properties could be read etc. Since getSize()
can return -1 by definition (and the order by trick to force getSize() have -1 returned is
just a "trick"), this is actually an improvement. Manually counting through the iterator is
the way to go without the trick.

> JCR-SQL2 : no count when WHERE clause is provided
> -------------------------------------------------
>
>                 Key: JCR-2765
>                 URL: https://issues.apache.org/jira/browse/JCR-2765
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Clemens Wyss
>
> whenever you provide a where-clause to a sql2 select, jcr/jackrabbit does not provide
the hit count.
> E.g.:
>    select * from [nt:unstructured]
>    order by [jcr:score]
> returns the hit count (query.execute().getRows().getSize()), 
> whereas
>   select * from [nt:unstructured]
>   where entity = "customer"
>   order by [jcr:score]
> doesn't.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message