The search schema is applied to the document, which is what's making a difference. It seems that the search schema was fixed between 5.0 and 6.0 to properly label the facet-value element as mixed content. In 5.0 it was a complex type without mixed content - meaning that you cannot calculate the string value of it.
John On 01/11/12 21:11, Will Thompson wrote: > In ML 5.0-3.3, this expression throws an exception: > > contains(<search:facet-value > xmlns:search="http://marklogic.com/appservices/search";>Some > value</search:facet-value>, " ") > => "XDMP-ARGTYPE ... arg1 is not of type xs:string?" > > But the parameter type isn't the problem - somehow it's related specifically > to the search namespace, since this works: > > contains(<search:facet-value xmlns:search="http://some-namespace";>Some > value</search:facet-value>, " ") > => true > > However, in ML 6.0-1.1, both expressions run without exceptions. Is this a > regression or a feature, or maybe an old bug that is now fixed in ML 6.0? > > -Will -- John Snelson, Lead Engineer http://twitter.com/jpcs MarkLogic Corporation http://www.marklogic.com _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
