OPTIMIZE ALL : <DBNAME>_224548755 could not be renamed
Friday, 22 February 2013 · 2 messages
FE
Fabrice Etanchaud22 Feb 2013 16:34 #
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
CG
Christian Grün22 Feb 2013 19:01 #
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
Quoted text · Fabrice Etanchaud · 32 lines
On Fri, Feb 22, 2013 at 4:34 PM, Fabrice Etanchaud <fetanchaud at 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 at mailman.uni-konstanz.de > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >
Written for BaseX 7.6. BaseX may have changed since: please check the current documentation.
⚡Generated with XQuery