Hi Fabrice,
we just had another use case in which a similar problem occurred, so this is surely something that should be fixed. Still, OPTIMIZE ALL is being used in productive use, so I’m wondering..
– if this problem occurs every time you are using OPTIMIZE ALL? – which you are using? – if you manage to make this reproducible for us?
Best, Christian
On Fri, Feb 22, 2013 at 4:34 PM, Fabrice Etanchaud fetanchaud@questel.com wrote:
Dear BaseX Team,
It seems to be a problem with the OPTIMIZE ALL command.
When applied on a <DBNAME> collection, it ends up with the following message : “<DBNAME>_224548755 could not be renamed”
I suppose a new optimized collection is being created aside the current one, and cannot be renamed as <DBNAME> at the end ?
Best regards,
Fabrice Etanchaud
Questel-Orbit
BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk