Hi Pascal,
this behavior is part of the BaseX transaction management. As XQuery
Update allows to alter multiple databases within the same query/transaction,
updating statements are executed in isolation - which means no other
transactions are allowed during evaluation of an updating transaction.
You can find more about this here [1]. But, depending on your use case,
there might be a workaround (i.e. performing updates on a copy, etc...).
Cheers,
Lukas
On Fri, Nov 4, 2011 at 3:39 AM, Pascal Heus
<pascal.heus@gmail.com> wrote:
All:
I'm running an long "xquery delete node" on one of my database and this
pretty much seem to make my server unavailable for other operations. I
expect this query to run for a few hours (affecting a few million nodes,
database is around 800Mb). I'm running this on a Amazon EC2 small
instance (1 CPU, 1.7Gb RAM) and the CPU has been stuck at 100%. If I
attempt to query any database on the server (not only the one being
updated), I basically don't get anything back. So do heavy xquery update
requests basically lock down the server? Anyone else having similar
experience? Feedback/suggestions?
best
*P
_______________________________________________
BaseX-Talk mailing list
BaseX-Talk@mailman.uni-konstanz.de
https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk