Trigger to apply statements on technical events ?
Tuesday, 12 May 2015 · 3 messages
C
cmarchand12 May 2015 08:34 #
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 ?
ChristopheCG
Christian Grün12 May 2015 09:18 #
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/1082Quoted text · cmarchand · 7 lines
> 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
CG
Christian Grün12 May 2015 09:19 #
Quoted text · Christian Grün · 1 line
> However, we are also working on the definition of locking operations
Ehrm, database triggers.
Quoted text · Christian Grün · 11 lines
> [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
Written for BaseX 8.1. BaseX may have changed since: please check the current documentation.
⚡Generated with XQuery