Take a look at the example in the cts:values documentation
http://docs.marklogic.com/cts:values. (Spoiler: You'll need a
cts:path-reference http://docs.marklogic.com/cts:path-reference.)
Justin
On Aug 18, 2015, at 10:27 AM, Paul M pjm...@yahoo.com wrote:
Suppose I want all the values for
On Tue, 18 Aug 2015 10:27:44 -0700, Paul M pjm...@yahoo.com wrote:
Suppose I want all the values for a specific path range index.Normally,
I would use cts:element-values and cts:frequencey on a range index. How
would I do this on a path range index, if possible.
Thank You.
Yes, use
...@developer.marklogic.com] On Behalf Of Paul M
Sent: Tuesday, August 18, 2015 10:28 AM
To: MarkLogic Developer Discussion
Subject: [MarkLogic Dev General] path range index
Suppose I want all the values for a specific path range index.
Normally, I would use cts:element-values and cts:frequencey on a range index
Suppose I want all the values for a specific path range index.Normally, I would
use cts:element-values and cts:frequencey on a range index. How would I do this
on a path range index, if possible.
Thank You.
___
General mailing list
Thanks,
Easy enough. ML8 doc little harder to search around.
-Paul
From: Danny Sokolsky danny.sokol...@marklogic.com
To: Paul M pjm...@yahoo.com; MarkLogic Developer Discussion
general@developer.marklogic.com
Sent: Tuesday, August 18, 2015 1:41 PM
Subject: RE: [MarkLogic Dev General
Hi All
My document model looks like below
Subject Area1
data
element1 active='2014-02-01T00:00:00'
inactive='-12-31T00:00:00'A/element1
element1 active='2013-01-01T00:00:00'
inactive='2014-01-31T00:00:00'B/element1
key active='2013-01-01T00:00:00'
your query for that value.
-Danny
From: general-boun...@developer.marklogic.com
[mailto:general-boun...@developer.marklogic.com] On Behalf Of
abhishek.srivas...@cognizant.com
Sent: Wednesday, April 08, 2015 5:44 PM
To: general@developer.marklogic.com
Subject: [MarkLogic Dev General] Path Range
Hi all,
I have a requirement to construct index on attributes. So based on the
performance
i just want to know the better option to go with either of
path-range-index/element-attribute-range index.
Which of the above will give best performance and recommended to go with.
Thanks,
Manoj
If //foo/@bar is the right precision, use an element-attribute range index. If
you need to specify a more general or a more precise XPath, use a path range
index.
Given the same precision there should be no difference in query performance,
because either index would contain the same values.
