On the BaseX Database Administration's Database page at
https://localhost:10443/BaseX/dba/databases, I selected a database I knew
was unoptimized and pressed the Optimize button. The database's COUNT
column decreased to the number entries in the database as expected.
However, the database's BYTES column did not change, even after I logged
off and back on to BaseX Database Administration.
Geoff Alexander, Ph.D.
Software Engineer, Corporate Tools Development
IBM Corporation
Charlotte, NC
From: "Christian Grün" <christian.gr...@gmail.com>
To: Geoff Alexander <gd...@us.ibm.com>
Cc: BaseX <basex-talk@mailman.uni-konstanz.de>
Date: 07/16/2020 01:10 PM
Subject: [EXTERNAL] Re: [basex-talk] Possible bug in database size
(bytes) after database optimize from BaseX Database
Administration
Hi Geoff,
Did you run OPTIMIZE ALL or db:optimize(..., true()) ? What do you mean by
"record count"?
Best,
Christian
Geoff Alexander <gd...@us.ibm.com> schrieb am Do., 16. Juli 2020, 18:06:
I've found that when I perform a database optimize on an unoptimized
database that while the record count decreases as expected, the database
size (bytes column) stay the same. Is this a bug in reporting the
database size (less severe problem) or a bug in the database not reducing
on optimize (more severe problem)? I've encountered this with both BaseX
8.6.7 and 9.3.3 running on Windows 10.
Thanks,
Geoff Alexander, Ph.D.
Software Engineer, Corporate Tools Development
IBM Corporation
Charlotte, NC
