Hi all, Using Basex 8.0, I notice a difference in behaviour compared to Basex 7.82 that I thought worth mentioning.
After creating a 5 GB db, then pruning it down to roughly 2GB using Xquery 'delete node', and after running db:optimize, in the GUI Result window I see vaaaast areas of white-space left over, presumably from where the nodes were deleted. Hundreds of screenfulls, actually.
Is this to do with the 'adaptive serialisation' that is now the default? Any options to use to prevent it? (it's not a huge problem, just midly annoying since with this particular DB I get a blank screen whenever I hit the 'Home' button in the GUI).
TIA, Constantine
________________________________
Elsevier B.V. Registered Office: Radarweg 29, 1043 NX Amsterdam, The Netherlands, Registration No. 33156677, Registered in The Netherlands.
Hi Constantine,
I'm not sure what may be the reason here. Could you possibly provide us with an SSCCE?
Thanks in advance, Christian
On Wed, Feb 11, 2015 at 9:33 PM, Hondros, Constantine (ELS-AMS) C.Hondros@elsevier.com wrote:
Hi all,
Using Basex 8.0, I notice a difference in behaviour compared to Basex 7.82 that I thought worth mentioning.
After creating a 5 GB db, then pruning it down to roughly 2GB using Xquery ‘delete node’, and after running db:optimize, in the GUI Result window I see vaaaast areas of white-space left over, presumably from where the nodes were deleted. Hundreds of screenfulls, actually.
Is this to do with the ‘adaptive serialisation’ that is now the default? Any options to use to prevent it? (it’s not a huge problem, just midly annoying since with this particular DB I get a blank screen whenever I hit the ‘Home’ button in the GUI).
TIA,
Constantine
Elsevier B.V. Registered Office: Radarweg 29, 1043 NX Amsterdam, The Netherlands, Registration No. 33156677, Registered in The Netherlands.
basex-talk@mailman.uni-konstanz.de
-
Christian Grün -
Hondros, Constantine (ELS-AMS)