Hi Seenivasan, what exactly do you want to do? What kind of subqueries are you thinking about? There are currently no plans to support concurrent subqueries of a query, so a single query (regard as sending one request to the database) is always one transaction. You can find more information on how we're locking in our [wiki]. [wiki]: http://docs.basex.org/wiki/Transaction_Management - - - On 2013-01-25 at 22:44 Christian Grün <christian.gruen@gmail.com> wrote:
One idea was to introduce a new pragma for explicitly locking parts of the code. This could look as follows:
(# db:lock #) { file:write(......) }
If you're looking for methods to implement your own locking (eg. for controlling access to external resources using our modules for files or HTTP access), this would be totally fine for you; but my main focus currently is at optimizing database locking (which is my thesis), so don't expect it to happen too soon (but it could happen earlier if somebody needs it). Kind regards from Lake Contance, Germany, Jens -- 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 22.01.2013 um 12:50 schrieb Seenivasan Gunabalan <seenivasan.gunabalan@dedalus.eu>:
Hi all, Is there a way to control concurrency from inside xqueries? Though its possible to achieve concurrency through REST (and RESTXQ?) interface, I am looking for ways to declaratively ask an xquery to run subqueries in a concurrent way.
Thanks in advance Seenivasan _______________________________________________ BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk