7 May
2014
7 May
'14
7:09 a.m.
Hi
2014-05-07 12:12 GMT+02:00 Christian Grün christian.gruen@gmail.com:
Considering the current penalty with calling optimize() after every change and otherwise (at least for me) no big differences in usage this would make an interesting use case
When it comes to optimize(), you could play around with the UPDINDEX option.
I did so. Two issues:
1) Path indexes are (according to the docs) dropped even with UPDINDEX
2) Full Text is excluded, so if you split your data over several databases (and have one dedicated to the full text data), you have to join this data again, which is quite noticeable already for around 50-100 nodes that you want to "join"
Christian