Hi,

Is there a way to prevent users of the BaseX GUI from modifying databases?

It seems that at least some of the database files need to be writable or else you can’t open the database. It also seems that the GUI gives you admin permission[1], making it possible for you to drop a database. I’ve been showing BaseX to more of my colleagues, and I want to protect against inadvertent modification of the databases that we are all sharing. Most of us use the GUI on Windows, and a few of us execute queries in standalone mode on various platforms.

A related question is whether it is problematic for one user of the GUI to have a database open (or to be actively running a query) while another user of the GUI is trying to run a query on the same database. Maybe a third user is executing a query in standalone mode at the same time. Assume all the queries are non-updating. The doc about transaction management[2] seems to suggest that you can have an arbitrary number of read transactions on the same database, which I take to mean that the different users will not interfere with each other. Is that correct and, if so, does it depend on a particular BaseX version?

Thanks,

Amanda

[1] http://docs.basex.org/wiki/User_Management

[2] http://docs.basex.org/wiki/Transaction_Management