So the database name which is being updated is based on variables passed in to the updating query, so I believe that would cause it to lock everything. 

Is there any way I can specify exactly what should be locked when going into an expression? Or better yet have basex lock nothing? From the documentation I thought that is what GLOBALLOCK would do, but it seems like even with that set to false it locks everything. 

I'm worried having everything lock for every updating query is going to be a real performance bottleneck


On Sat, Nov 2, 2013 at 10:55 AM, Jens Erat <jens.erat@uni-konstanz.de> wrote:
Hi Joe,

concurrency in BaseX still has some [limitations]. Possibly one of these is triggering a global lock in your case. You can find out what locks a query is triggering by running it in the GUI and looking at the "Query Information“ pane or on the command line by using `SET QUERYINFO ON`.

If you’re unsure what’s triggering the global lock in your case, feel free to send the query to either the mailing list or directly to me. Could take some time for an answer though as I’m currently abroad.

Regards,
Jens


[limitations]: http://docs.basex.org/wiki/Transaction_Management#Limitations

--
Jens Erat

 [phone]: tel:+49-151-56961126
  [mail]: mailto:email@jenserat.de
[jabber]: xmpp:jabber@jenserat.de
   [web]: http://www.jenserat.de

     PGP: 350E D9B6 9ADC 2DED F5F2  8549 CBC2 613C D745 722B



Am 01.11.2013 um 11:49 schrieb Joe Templeman <joe@inkling.com>:

> Hi, I've e-mailed before about this issue, but that was a while ago so I wanted to start a new thread.
>
> I'm currently experiencing a situation where all calls (updating or otherwise) are being blocked by any updating call within the same database, even when GLOBALLOCK is set to false.
>
> The setup is that we have a restxq endpoint which is checks if the requested content is loaded and if it isn't, we use a java library to fetch the content and then add it to the database. We return a restxq:forward, to the requested endpoint which thens processes the request, assuming the content exists.
>
> For some reason however, even with GLOBALLOCK set to false,
> _______________________________________________
> BaseX-Talk mailing list
> BaseX-Talk@mailman.uni-konstanz.de
> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk