[MarkLogic Dev General] max function alternatives UPDATED

Patrick Force patrickf at arc90.com
Thu Jan 11 12:12:43 PST 2007


Sorry for the confusion.  My initial post used generic values as  
reference points and I accidentally used the real element/attribute  
names when I displayed the query.  My actual attribute index and  
XQuery as I've set it:

element QName: InsurancePolicy
attribute QName: index

cts:element-attribute-values(xs:QName("InsurancePolicy"),xs:QName 
("index"))

Sorry for the confusion.  With that in mind, should we upgrade to  
3.1-4?  It's seeming more and more like this might be a support/ 
upgrade issue in the attribute index setting.  Thanks again.

Patrick

Hi Patrick,

In looking again at what you are trying to do, I think perhaps you have
set up the index on the wrong element/attribute conbination.  I may not
have this correct, but based on what it says below, here is what I see.

Below, you say you have an index on the following:
   element QName: RootElement
   attribute QName: index

But the query you are trying to perform is this:

cts:element-attribute-values(xs:QName("InsurancePolicy"),xs:QName("id"))


This query requires the range index on:
   element QName: InsurancePolicy
   attribute QName: id

So I guess the thing to verify is exactly what index do you have
created, and exactly what query are you trying to perform.

-Danny


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://xqzone.marklogic.com/pipermail/general/attachments/20070111/a7c21d05/attachment.html


More information about the General mailing list