vpro / jcr-criteria Goto Github PK

With that you can restrict the results to a items with certain jcr:uuid.

Btw, naively doing Restrictions.in(attr('jcr:uuid'), '') doest work. I don't quite get why. Probably the jcr:uuid is not indexed like that, and whhen simply using 'eq' jackrabbit is smart enough to get them by id directly.

anyways, this implementation can hide all these kind of implementation details.

This log seems misleading as the queryCount is always executed.

ro.jcr.criteria.advanced.impl.AdvancedCriteriaImpl: Total size was not available, determining it took 1341 ms

There isn't an alternative path that doesn't execute the queryCount.

Hey,

could you please trigger another release?
@mihxil tried to create one after I asked for it in #11, but it failed.

Thanks and kind regards,
Björn

In order to be able to compare Criteria objects, they should implement equals() and hashCode() methods.

Calling criteria.setBasePath("/site/news") results in this XPath expression: //site/news//*

This could match multiple 'base' paths, like /a/site/news/test and /b/site/news/test, but even if /site/news/test is the only path that matches this query, it would be more efficient to query /jcr:root/site/news//* than //site/news//*.

Performance, especialy when using SQL seems to be bad.

In cases where there is no ordering it is possible for the counting of the query to return -1 causing an infinite loop of the count query.

XPath is deprecated long time. I think it would not be hard to support doing things via SQL2.