[Exist-open] Data Corruption Workaround

[Costas M. <km...@is...>]

Hi everyone

In the past, I had writen to this list to report data corruption problems I had
using Xupdate. (http://article.gmane.org/gmane.text.xml.exist/4366)

THE PROBLEM ----
In summary, the xupdate to replace an existing node...

<xu:modifications version="1.0" xmlns:xu="http://www.xmldb.org/xupdate">
  <xu:insert-before select="//document[ <at> id='a2481'][1]">
    <document id="a2481" name="Development"/>
  </xu:insert-before>
  <xu:remove name="doc" select="//document[ <at> id='a2481'][2]"/>
</xu:modifications>};

...would result in frequent (twice a day), undeterministic data corruptions. )-:

WORKARROUND ----

Two weeks ago I substituted the <xu:insert> and <xu:remove> steps with the
non-standard (exist-db only extention ?!) <xu:replace>.

Since then I haven't had a single data corruption incindent (-:

I hope that this observation might help Wolfgang to pinpoint the possible cause
and other people to better enjoy eXist.

rgrds
costas