Hello !
I've had this problem : I've forgotten a db:optimize(...) after a delete nodes operation. The following xquery has been 60 times slower than before. Is there a way to detect an update operation, and a way to know on which database the update occurs, to run automatically a db:optimize(...) each time a update xquery is run ?
Christophe
Hi Christophe,
the AUTOOPTIMIZE option might do what you want [1]: If applied to a database, it will always be optimized after an update operation. However, we are also working on the definition of locking operations [2].
Best, Christian
[1] http://docs.basex.org/wiki/Options#AUTOOPTIMIZE [2] https://github.com/BaseXdb/basex/issues/1082
I've had this problem : I've forgotten a db:optimize(...) after a delete nodes operation. The following xquery has been 60 times slower than before. Is there a way to detect an update operation, and a way to know on which database the update occurs, to run automatically a db:optimize(...) each time a update xquery is run ?
Christophe
However, we are also working on the definition of locking operations
Ehrm, database triggers.
[1] http://docs.basex.org/wiki/Options#AUTOOPTIMIZE [2] https://github.com/BaseXdb/basex/issues/1082
I've had this problem : I've forgotten a db:optimize(...) after a delete nodes operation. The following xquery has been 60 times slower than before. Is there a way to detect an update operation, and a way to know on which database the update occurs, to run automatically a db:optimize(...) each time a update xquery is run ?
Christophe
basex-talk@mailman.uni-konstanz.de
-
Christian Grün -
cmarchand＠oxiane.com