database corruption after update query

On Mon, Dec 19, 2011 at 10:26 AM, Adrian Hossu <adibadi at gmail.com> wrote: > Hello all, > > first the info: > basex 7.0.2 > debian 64bit > jre 1.6.0_30-b12 > > We are experiencing some strange behaviour with basex - certain update > queries are causing our database to become corrupted, and we need to drop > the database and re-import in order to be able to continue. Here is an > example of such a query: > > replace node > collection("ft")/user/user[@id='2']/logsheets/logsheet[@date='2011-12-20']/exercise[2] > with <exercise/> > > The query executes successfully, however, executing db:list('ft') after this > call gives us only garbled text. The basexgui shows the results of this as: > &#x0D;&#x16;&gt;&#x95;&#x04;_'蘼&#x01; &#x0D;&#x16 ..................etc.... > Perhaps it's the query, or our original data which we are starting with? > > Any help would be greatly appreciated. > > best regards, > Adrian

On Mon, Dec 19, 2011 at 5:51 PM, Christian Grün <christian.gruen at gmail.com> wrote: > Dear Adrian, > > thanks for reporting this issue, which should be fixed as soon as > possible. First of all: does it also occur with the latest snapshot > (7.1 beta, [1])? If yes, do you think you can create an sccee [2] that > allows us to reproduce the problem? > > Christian > > [1] http://files.basex.org/releases/latest > [2] http://sscce.org > ___________________________ > > On Mon, Dec 19, 2011 at 10:26 AM, Adrian Hossu <adibadi at gmail.com> wrote: >> Hello all, >> >> first the info: >> basex 7.0.2 >> debian 64bit >> jre 1.6.0_30-b12 >> >> We are experiencing some strange behaviour with basex - certain update >> queries are causing our database to become corrupted, and we need to drop >> the database and re-import in order to be able to continue. Here is an >> example of such a query: >> >> replace node >> collection("ft")/user/user[@id='2']/logsheets/logsheet[@date='2011-12-20']/exercise[2] >> with <exercise/> >> >> The query executes successfully, however, executing db:list('ft') after this >> call gives us only garbled text. The basexgui shows the results of this as: >> &#x0D;&#x16;&gt;&#x95;&#x04;_'蘼&#x01; &#x0D;&#x16 ..................etc.... >> Perhaps it's the query, or our original data which we are starting with? >> >> Any help would be greatly appreciated. >> >> best regards, >> Adrian

> Dear Adrian, > > thanks for reporting this issue, which should be fixed as soon as > possible. First of all: does it also occur with the latest snapshot > (7.1 beta, [1])? If yes, do you think you can create an sccee [2] that > allows us to reproduce the problem? > > Christian > > [1] http://files.basex.org/releases/latest > [2] http://sscce.org > ___________________________ > > On Mon, Dec 19, 2011 at 10:26 AM, Adrian Hossu <adibadi at gmail.com> wrote: > > Hello all, > > > > first the info: > > basex 7.0.2 > > debian 64bit > > jre 1.6.0_30-b12 > > > > We are experiencing some strange behaviour with basex - certain update > > queries are causing our database to become corrupted, and we need to drop > > the database and re-import in order to be able to continue. Here is an > > example of such a query: > > > > replace node > > > collection("ft")/user/user[@id='2']/logsheets/logsheet[@date='2011-12-20']/exercise[2] > > with <exercise/> > > > > The query executes successfully, however, executing db:list('ft') after > this > > call gives us only garbled text. The basexgui shows the results of this > as: > > &#x0D;&#x16;&gt;&#x95;&#x04;_'蘼&#x01; &#x0D;&#x16 > ..................etc.... > > Perhaps it's the query, or our original data which we are starting > with? > > > > Any help would be greatly appreciated. > > > > best regards, > > Adrian >