Hi Srini,
thanks for your report. I could reproduce the bug, even with the standalone version of BaseX. The issue is related to our buggy locking downgrades, which we reactivated some weeks ago (too early, as it seems). I have added a GitHub issue [1] to track down the behavior, and I have uploaded a new stable snapshot [2]. Please expect a BaseX 7.7.1 bug fix release in September.
Best, Christian
[1] https://github.com/BaseXdb/basex/issues/745 [2] http://files.basex.org/releases/latest/ ___________________________
We have been using basex 7.7 snapshot from June 20 and wanted to upgrade to the release version but looks like I have hit a bug with BaseX 7.7 release version while running a set of xqueries in sequence. I am able to reproduce this in BaseX 7.7 running in client-server mode on two different machines. Here are the steps to reproduce:
- Launch BaseX 7.7 server (with defaults)
- Launch BaseX command line client (run the file under bin/basexclient.bat
that comes in zip) and run the following commands (also attached a screenshot):
Username: admin Password: BaseX 7.7 [Client] Try help to get more information.
create db d1 <hello/>
Database 'd1' created in 103.22 ms.
xquery delete node doc('d1')//oops
Query executed in 25.03 ms.
xquery let $doc := 'd1' return doc($doc)
At this point BaseX 7.7 server cannot be stopped using the stop batch file and I have to kill all processes using Task Manager.
These set of commands works fine on BaseX 7.7 snapshot from June 20th.
Let me know if this is a bug or am I missing something here.
Thanks, Srini
BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk