Hi Charles, thanks Phil,
two years ago, we still have warned everyone to *avoid* BaseX for critical write operations. As (due to our history) most of our users have come across BaseX in the search for a efficient read-only solution, we have spent most of our time in optimizing read-only use case.
Since that time, we have put quite some effort into making update operations more robust, fixing remaining low-level bugs, writing stress tests, etc. We now use BaseX and XQuery Update successfully for our own write scenarios without any further complications, and we are convinced that BaseX is now at least as safe as other native XML database solutions.
While we cannot promise the same stability as is offered by 10, 20 year old RDBMS solutions, we will further do our best to debug (ideally reproducible) cases in which write problems persist.
Comments are welcome, Christian ___________________________
On Mon, Mar 14, 2011 at 11:04 PM, NewIntellectual newintellectual@gmail.com wrote:
In fairness it is worth noting that XQuery Update facility 1.0 is extremely new. See e.g. http://www.w3.org/TR/xquery-update-10/, dated 25 January 2011. I don't know of any other open source system which even attempts to completely support as many XQuery standards, such as XQuery Full Text and and the update facility.