For the record, this issue has been fixed in latest release.. Cheers
On 2/13/15, 10:14 AM, "Geert Josten" <[email protected]> wrote: >Sounds like a bug. Are you able to report it yourself? > >Kind regards, >Geert > >On 2/13/15, 9:02 AM, ""neil bradley"" <[email protected]> wrote: > >>I cant see why this causes a XDMP-CONFLICTINGUPDATES error. I am >>replacing a node in the document and a node in its properties, which I >>think should not conflict with each other. >> >> xdmp:document-insert("/MyDoc.xml", <D1><D2/></D1>) >> , >> xdmp:document-set-properties("/MyDoc.xml", <P1><P2/></P1>) >> ; >> xdmp:node-replace(fn:doc("/MyDoc.xml")/D1/D2, <D3/>) >> , >> >>xdmp:node-replace(xdmp:document-properties("/MyDoc.xml")/prop:properti >>es/P1/P2, <P3/>) >> >>I get the same error whatever I do. For example I tried this approach >>instead: >> >> xdmp:node-replace(fn:doc("/MyDoc.xml")/D1/D2, <D3/>) >> , >> xdmp:node-replace(fn:doc("/MyDoc.xml")/property::P1/P2, <P3/>) >> >>So I tried just overwriting the main document (which should not >>overwrite the properties file), and that works fine: >> >> xdmp:document-insert("/MyDoc.xml", <D3/>) >> , >> xdmp:node-replace(fn:doc("/MyDoc.xml")/property::P1/P2, <P3/>) >> >>So why is it NOT a conflict when I completely replace the main >>document fragment, but it IS a conflict when I just replace a node >>within it? >> >>Neil. >>_______________________________________________ >>General mailing list >>[email protected] >>http://developer.marklogic.com/mailman/listinfo/general > >_______________________________________________ >General mailing list >[email protected] >http://developer.marklogic.com/mailman/listinfo/general _______________________________________________ General mailing list [email protected] Manage your subscription at: http://developer.marklogic.com/mailman/listinfo/general
