jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Lukin <lu...@stu.cn.ua>
Subject SQL query processing bug?
Date Mon, 11 Feb 2008 21:02:53 GMT
Hi, all!
Being disparate with XPath query performance I tried SQL query and results  was even worse.

Queries:
 
1: "SELECT * FROM nt:base WHERE jcr:path LIKE '/foo/bar[%]/%'"
2: "SELECT * FROM nt:base WHERE jcr:path LIKE '/foo/bar[%]/%'/%"
2: "SELECT * FROM nt:base WHERE jcr:path LIKE '/foo/bar[%]/%'/%/%"

Query 1,2, and 3 give the same results - nodes at /foo/bar. Only difference is: query 2 runs
longer that 1, 3 longer that 2.
BTW, too long (12 sec q. 3) for my 10 nodes in "bar" level with 40 nodes under "bar/%/". 
I looked at source of jackrabbit query tests and  found path queries with only one "%" sign
at end so I think that this kind of query just untested.

Could you guys test such queries on your setup, may be it is bug? 
-- 
SY, Alex Lukin
RIPE NIC HDL: LEXA1-RIPE

Mime
View raw message