Hmm, I seem to get the same error regardless of set "true" or "false" - so 
perhaps the first question, am I sure each argument is a single node?  It 
should be yes, but it's happening more than once - to put in context, the same 
"firm" can exist in multiple parts of these docs because the doc describes a 
case history, and several points of where they were representedBy for different 
causes and actions.

I do have 3 For loops in my script - maybe there's a nesting that is causing 
this behavior; let me know if you have another idea of what I might check.  

[1.0-ml] XDMP-CONFLICTINGUPDATES: xdmp:eval("xquery version 
&quot;1.0-ml&quot;;&#10;declare namespace html = ...", (), <options 
xmlns="xdmp:eval"><database>4793418423724769125</database><modules>529627520719988...</options>)
 

-- Conflicting updates 

xdmp:node-replace(fn:doc("/olympus/pacer-xml/1155991_2:13-cv-00188")/case/parties/party[1]/representedBy/counsel/firmname,
 <firmname>$translation/text()</firmname>) 

and 
xdmp:node-replace(fn:doc("/olympus/pacer-xml/1155991_2:13-cv-00188")/case/parties/party[1]/representedBy/counsel/firmname,
 <firmname>$translation/text()</firmname>)


-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of Christopher Hamlin
Sent: Monday, May 11, 2015 7:42 PM
To: MarkLogic Developer Discussion
Subject: Re: [MarkLogic Dev General] xdmp:node-replace

Hi

You get the error with just a single node-replace call?

Are you sure each argument is a single node?

If you left function-mapping on, it might not create the error you think it 
would, so you could try adding the option

declare option xdmp:mapping "false";

to turn it off, then see if the error makes more sense.

/ch
_______________________________________________
General mailing list
[email protected]
Manage your subscription at: 
http://developer.marklogic.com/mailman/listinfo/general



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

Reply via email to