Database-level locking
Friday, 22 November 2013 · 2 messages · last reply 24 Nov 2013
CD
Charles Duffy22 Nov 2013 17:16 #
Howdy --
Something I'd like to see would be the ability to make assertions about which databases a query will need a write lock on, such that the queries will fail at runtime if such an assertion was made but more locks are needed than were declared.
This could allow more fine-grained locking to be used in places where global locks presently apply, without loss of safety.
...or is there an existing alternative that I've missed?
CG
Christian Grün24 Nov 2013 19:12 #
Hi Charles,
currently, there is no such option in BaseX, but I’ve added an issue [1]; let’s see if some more people give feedback on this.
Thanks,
Christian
[1] https://github.com/BaseXdb/basex/issues/802
Quoted text · Charles Duffy · 18 lines
On Fri, Nov 22, 2013 at 4:16 PM, Charles Duffy <charles at dyfis.net> wrote: > Howdy -- > > Something I'd like to see would be the ability to make assertions about > which databases a query will need a write lock on, such that the queries > will fail at runtime if such an assertion was made but more locks are needed > than were declared. > > This could allow more fine-grained locking to be used in places where global > locks presently apply, without loss of safety. > > ...or is there an existing alternative that I've missed? > > _______________________________________________ > BaseX-Talk mailing list > BaseX-Talk at mailman.uni-konstanz.de > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >
Written for BaseX 7.7. BaseX may have changed since: please check the current documentation.
⚡Generated with XQuery