Hi all,
New to Marklogic and setting up a new dev server (4.2-8), existing server is
4.2-4, and finding that our current Xquery scripts aren't working on the new
server setup.
It seems the namespaces setup in the database Element Range Indexes etc aren't
found (we have to add the namespace
Hi Anshu,
It is correct that you need to declare namespaces in your XQuery to
address Range indexes that use them. It is because indexes work with
qualified names (QNames), so you need both a namespace (uri or prefix
bound to uri) and a local name to be able to address the right QName from
you
Thanks for the response.
We are using it in the main module and xquery version has been declared
as 'xquery version 1.0-ml;'.
Regards,
Anshu
On 25/01/2012 12:45, Geert Josten wrote:
Hi Anshu,
It is correct that you need to declare namespaces in your XQuery to
address Range indexes that use
Geert, The version of Marklogic is 4.2-3.2
Best Regards,
Kashif Khan
Sr. Solutions Architect
Houghton Mifflin Harcourt, Orlando, FL
Office: (407) 345-3420
Cell: (407) 949-4697
The water you touch in the river is the last of that which has passed and the
first of that which is coming --Leonardo
Hi Kashif,
Are you sure you are passing in the options as given in your own example
code? The error message seems to show a second searchable-expression
element, directly underneath the options element. I suspect that is causing
the trouble here: there are two searchable-expression elements in
We have a working pipeline with a condition element and an action element,
as would be expected. We now need to in essence add a second condition,
where we would need both conditions to be evaluated, and if either returned
true, then the same action gets executed.
We do NOT wish to change the
Hi David,
If I understand correctly what you are trying to do, it should work by:
* Taking the first state-transition and changing its success action to
be a no-op or similar.
* Adding a second state-transition that responds to the success of the
first one, and putting your
On Wed, 25 Jan 2012 10:58:17 -0800, David Swearingen
dswearin...@42six.com wrote:
We have a working pipeline with a condition element and an action
element, as would be expected. We now need to in essence add a second
condition, where we would need both conditions to be evaluated, and
