Thanks to all for your replies.

That has fixed the problem.

A colleague managed to fix it by using the:

declare default collation "http://marklogic.com/collation/codepoint";;

But that broke in the Query Console - so this is best outcome. That also 
explains why a range was working for an xs:date.

I'm still unsure about why this was working from the Roxy tests - but I can 
live with not knowing, as I can checkin the code now :-)

Thanks again,

Dec


On 30 Nov 2012, at 19:42, Danny Sokolsky <[email protected]> wrote:

> As Mike said, the collation is a good thing to double-check.  It is best 
> practice to specify the collation in the range constraint, that way you will 
> not have to worry about default collation.  So make sure your constraint has 
> the collation specified.  Something like:
>  
> <options xmlns="http://marklogic.com/appservices/search";>
> <constraint name="name">
>    <range type="xs:string" collation="http://marklogic.com/collation/";>
>      <element ns="" name="name"/>
>    </range>
> </constraint>
> </options>
>  
> Another hint is to look very closely at the entire error you are getting—it 
> often has useful info that is easy to miss.
>  
> If you still cannot figure it out, post some code that we can look at and 
> then maybe we can go from there.
>  
> -Danny
>  
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of Mike Sokolov
> Sent: Friday, November 30, 2012 9:34 AM
> To: MarkLogic Developer Discussion
> Cc: Fahad Khan
> Subject: Re: [MarkLogic Dev General] Odd app server behaviour
>  
> You might also have a different default collation - that's my guess, since it 
> is configurable per-appserver
> 
> On 11/30/2012 10:07 AM, Fahad Khan wrote:
> Hello,
> 
> Whenever I have this issue it turns out to be name-space related. I am 
> guessing you have double checked that too?
> 
> Fahad.
> 
> 
> 
> On 11/30/2012 02:35 PM, Declan Newman wrote:
> Hello,
>  
> I'm having a very odd problem with ML v6.0-2.
>  
> I have my range element indexes all set-up for the elements that I wish to 
> facet on.
>  
> I am able to call the function that calls 
>  
> search:search($searchTerm, $search-options, ($page - 1) * $itemsPerPage + 1, 
> $itemsPerPage)}
>  
> from qconsole and the facets are returned correctly - but as soon as I call 
> this function from within an app I receive the error "No element range index" 
> … with the list of indexes that I have double checked exist as 
> element-range-index.
>  
> I have also double/triple/quadruple-checked that the app is talking to the 
> correct database.
>  
> Is there something I'm missing here? I'm currently stumped.
>  
> Thanks,
>  
> Dec
>  
>  
> ----------------------------------------------------------------------------
> Declan Newman, Development Team Lead,
> Semantico, Floor 1, 21-23 Dyke Road, Brighton BN1 3FE
> <mailto:[email protected]>
> <tel:+44-1273-358247>
>  
> 
> 
> 
> _______________________________________________
> General mailing list
> [email protected]
> http://developer.marklogic.com/mailman/listinfo/general
>     
> 
> 
>  
>  
> _______________________________________________
> General mailing list
> [email protected]
> http://developer.marklogic.com/mailman/listinfo/general
>   
> _______________________________________________
> General mailing list
> [email protected]
> http://developer.marklogic.com/mailman/listinfo/general

----------------------------------------------------------------------------
Declan Newman, Development Team Lead,
Semantico, Floor 1, 21-23 Dyke Road, Brighton BN1 3FE
<mailto:[email protected]>
<tel:+44-1273-358247>

_______________________________________________
General mailing list
[email protected]
http://developer.marklogic.com/mailman/listinfo/general

Reply via email to