Hi Kary,
Send us the XML samples along with your code snippet (that you want to
perform exactly). I can help you to make it works.
Regards,
Indy
On Tue, May 12, 2015 at 9:11 PM, Christopher Hamlin <cbham...@gmail.com>
wrote:
> Hi,
>
> You can't make two changes to the same node, but somehow that is what
> is happening. In this case you are making two changes to
>
>
> fn:doc("/olympus/pacer-xml/1155991_2:13-cv-00188")/case/parties/party[1]/representedBy/counsel/firmname
>
> The definition says:
>
> ====================
> Cause
>
> The application attempted to perform multiple updates to the same
> document within the same transaction.
>
> A single statement may not perform more than one update to the same
> document. For example, you cannot update a node and add a child
> element to that node in the same statement.
>
> Response
>
> Revise your application code to perform the conflicting operations in
> two separate statements. For example, use the semicolon transaction
> delimiter, or execute the second update inside an xdmp:eval with the
> isolation option set to different-transaction.
> ====================
>
> There is a bit more info here:
>
>
> https://help.marklogic.com/knowledgebase/article/View/25/16/xdmp-conflictingupdates-and-how-to-avoid-it
>
> Maybe use xdmp:log and instead of making the change, log the
> URIs/xpath/whatever. Then you would see what's going on and whether
> it is what you expect. You can use xdmp:describe to dump things out.
> Note that it will truncate by default, but that can be overridden.
>
> /ch
> _______________________________________________
> General mailing list
> General@developer.marklogic.com
> Manage your subscription at:
> http://developer.marklogic.com/mailman/listinfo/general
>
_______________________________________________
General mailing list
General@developer.marklogic.com
Manage your subscription at:
http://developer.marklogic.com/mailman/listinfo/general
