> I confirm the problem : on another database (same data, same script.xbs,
> different server), we have exactly the same problem : the database grows
> each time the script is run.
>
> I'm going to prepare a test-case with small public data tonight.
Same here: Using the latest version of BaseX sho
James, you are right, OPTIMIZE ALL solves the problem.
The txt.basex was growing at each replace, other files staying almost
identical.
Thanks a lot !
Best regards,
Christophe
Le 03/09/2015 21:20, basex-talk-requ...@mailman.uni-konstanz.de a écrit :
Send BaseX-Talk mailing list submissions t
James, you are right, OPTIMIZE ALL solves the problem.
Thanks a lot !
Best regards,
Christophe
Le 03/09/2015 21:20, basex-talk-requ...@mailman.uni-konstanz.de a écrit :
Send BaseX-Talk mailing list submissions to
basex-talk@mailman.uni-konstanz.de
To subscribe or unsubscribe via the W
Message: 1
Date: Thu, 03 Sep 2015 14:59:53 +0200
From: cmarch...@oxiane.com
To: basex-talk@mailman.uni-konstanz.de
Subject: Re: [basex-talk] size on collection in the time (Marc)
Message-ID: <2fe47eb3ff5f77da91888afed19d2...@oxiane.com>
Content-Type: text/plain; charset="u
e I
did a full optimise. My suggestion is next time to try a full optimise instead
of dropping the collection and see if that helps.
Regards, James
Message: 1
Date: Wed, 2 Sep 2015 17:36:19 +0200
From: Marc
To: BaseX
Subject: [basex-talk] size on collection in the time
Message-ID: <
I confirm the problem : on another database (same data, same script.xbs,
different server), we have exactly the same problem : the database grows
each time the script is run.
I'm going to prepare a test-case with small public data tonight.
Best regards,
Christophe
Hello Dirk,
We use a Ba
was only around 600MB once I
did a full optimise. My suggestion is next time to try a full optimise instead
of dropping the collection and see if that helps.
Regards, James
>
> Message: 1
> Date: Wed, 2 Sep 2015 17:36:19 +0200
> From: Marc
> To: BaseX
> Subject: [b
Hello Dirk,
We use a BaseX script (.xbs) with a list of REPLACE.
We try to investigate this point if this is reproducable or not.
If I find this problem again, I take a copy of the collection before to
delete her.
Thank you for answer.
Marc
Le 03/09/2015 09:52, Dirk Kirsten a écrit :
Hello Ma
Hello Marc,
sure, a replace should lead to a true replace, i.e. the old data will be
dropped. So this sounds like a bug, but it is difficult to replicate
from what you describe.
Do you think it would be possible to make the issue reproducable, maybe
also with a smaller data set? Also, how exactly
Hi,
I have a remark about the size of the files of a collection.
We do a lot of updates (REPLACE) with an attributes index but without a
text index.
I see that the size of the files grows up in the time we arrive until
30Go until the limit of the filessytems quota.
When I drop the collection and
10 matches
Mail list logo
