Keith, In your second example, the additional-query element is not in the http://marklogic.com/appservices/search namespace.
Justin On Mar 17, 2011, at 1:54 PM, Keith L. Breinholt wrote: > I'm running 4.2-2 and have run into a search:search() scenario where if I > create the <options> element textually I get the expected results but if I > <additional-query> elements in the <options> element programmatically it > returns all values in the result set as if the additional-query element(s) > don't exist. > > What is the different between doing this: > > let $opt := > <options xmlns="http://marklogic.com/appservices/search";> > <searchable-expression>{"/something"}</searchable-expression> > <additional-query>{cts:element-value-query( > xs:QName("format"), ("xls","xlsx") )}</additional-query> > </options> > > And this: > > let $query := <additional-query>{cts:element-value-query( > xs:QName("format"), ("xls","xlsx") )}</additional-query> > let $opt := > <options xmlns="http://marklogic.com/appservices/search";> > <searchable-expression>{"/something "}</searchable-expression> > {$query} > </options> > > The first returns the expected result. The second returns all results as if > the additional-query was never applied. > > Keith L. Breinholt > "Do what you can, with what you have, where you are." - Theodore Roosevelt > > > NOTICE: This email message is for the sole use of the intended recipient(s) > and may contain confidential and privileged information. Any unauthorized > review, use, disclosure or distribution is prohibited. If you are not the > intended recipient, please contact the sender by reply email and destroy all > copies of the original message. > > > _______________________________________________ > General mailing list > [email protected] > http://developer.marklogic.com/mailman/listinfo/general _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
