Hi Justin, Alas, I didn't keep the stack output from the query console - but suffice to say that it was the same problem that I was having in reverse: "No element range index" (before it worked in the console but failed in the app server) - I tried adding 'declare default collation "http://marklogic.com/collation/codepoint";;' but it didn't have any effect.
My colleague found a post from Rob Whitby <https://github.com/robwhitby/xray/issues/6> - that along with your help identified that it was down to the collations. If I can help further in any way, please let me know. Thanks, Dec On 30 Nov 2012, at 20:31, Justin Makeig <[email protected]> wrote: > Declan, > Can you help me understand how the default collation “broke in Query > Console”? Was the Query Console UI not able to handle that? Were the results > not as expected? Any details would help to improve Query Console. Thanks. > > Justin > > > Justin Makeig > Director, Product Management > MarkLogic Corporation > [email protected] > Phone: +1 650 655 2387 > www.marklogic.com > > > > On Nov 30, 2012, at 12:28 PM, Declan Newman <[email protected]> > wrote: > >> 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 > > _______________________________________________ > 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
