Ganaprakash, That first form is a 4-way OR so may be slightly more complex to build, though I don't see it on my machine.
This line - the actual building of the constraint structure - is likely to have a minor performance impact compared to the actual query execution. Is there a reason you want to optimize this line? Yours, Damon From: general-boun...@developer.marklogic.com [mailto:general-boun...@developer.marklogic.com] On Behalf Of gnanaprakash.bodire...@cognizant.com Sent: Saturday, May 03, 2014 11:34 AM To: general@developer.marklogic.com Subject: [MarkLogic Dev General] path range query taking more time when multiple values are supplied Hi I am profiling one of my queries and found that path range query is taking more time when multiple values are passed. Example: cts:path-range-query("*:resource/*:level/*:level/*:level/@type","=",("module","lesson","unit","day") ,$case-insensitive-collation) Shallow µs: 600-900 takes more time than cts:path-range-query("*:resource/*:level/*:level/*:level/@type","=","module",$case-insensitive-collation) Shallow µs: 60-80 Is this expected behaviour? Is there any other alternative approach of using multiple values based path range query? Regards, Gnanaprakash Bodireddy This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient(s), please reply to the sender and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email, and/or any action taken in reliance on the contents of this e-mail is strictly prohibited and may be unlawful.
_______________________________________________ General mailing list General@developer.marklogic.com http://developer.marklogic.com/mailman/listinfo/general
