Am 03.06.15 um 11:40 schrieb Alexander Klimetschek: > On 02.06.2015, at 16:39, Carsten Ziegeler <[email protected]> wrote: >> The query contains the sort information (which properties and whether >> ascending or descending), so you can get the values of the props and >> compare them. > > But then you need to > > a) be able to understand and fully evaluate the query on the aggregate level
Nope, just the sorting > b) cannot use an index for that and do a property read for every result entry It's true, the property is read for every entry - but only(!) if there is more than one resource provider providing results. > > I am just saying, you are getting into a very complex and performance > critical business. And even if you say "users won't use such edge-case > queries, it's ok if we don't look for perfect performance", they will use it > (experience tells me, people always find ways to run difficult & slow queries > :D), and then you have just created a new performance critical area out of > nowhere. Well, let's agree that we disagree here. For the majority of users, there is only JCR anyway, which means there is no difference between using a nice api and fiddling with strings by hand when it comes to performance. Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland [email protected]
