On the page about transaction management [1], the wiki says:

As the standalone versions of BaseX (command-line, GUI) cannot be synchronized with other BaseX instances, we generally recommend working with the client/server architecture if concurrent write operations are to be performed.

Am I right to interpret this as meaning that I can work safely in the BaseX GUI interface while the http version (or a servlet version) of BaseX is running at the same time, if any of the following conditions are observed?

1 The GUI and the server or servlet have different settings for DBPATH.

2 They are working with different databases.

3 One or the other of the interfaces is only reading, not writing, the database.

Apart from wishing to understand the situation in general terms, the practical question I'm currently wondering about is how to make it safe for myself to have a version of BaseX running in the background managing a local database or two through a Web interface, while still being able to pop in to the GUI from time to time to do some quick queries. I rarely want to use the GUI for the databases for which I have Web interfaces, so if it's necessary to use a separate DBPATH, I could probably live with that. But sometimes it's convenient, so if I can get by, relying on point 3, that would be excellent.