OK, so reads during a write will not be blocked but concurrent writes will be? Also how does Exist-DB know which database to lock? In BaseX it's very limited so it will only lock the database if the name of the database is hard coded in the script (otherwise it locks every database), which was an issue since the databases which are accessed are based on the request which is received (we use a restxq API). 

The locking in BaseX is also considerably more aggressive, and we have to lock out all other read requests whenever a write is happening, this is causing performance issues so we're considering the move to exist-db.


On Tue, Nov 26, 2013 at 4:06 AM, Dannes Wessels <dizzzz@exist-db.org> wrote:

> On 19 Nov 2013, at 07:35, Joe Templeman <joe@inkling.com> wrote:
> When content is being loaded into a given database, are all other write queries blocked? Are all other read queries blocked?

No, not all other write queries are blocked, but as far as I remember it is not possible to write simultaneously into one collection. If that is really a problem, I could not say (wolf?)

Reading/querying should always work.