Changes

The BaseX client-server architecture offers ACID -safe transactions,with multiple readers and writers. Here are is some moreinformations information about the transaction management.

=TransactionIntroduction=

Incoming requests are parsed and checked for errors on the server. If the command or query is not correct, the request will not be executed,and the user will receive an error message. Otherwise the request becomes a transaction and gets into the transaction monitor.

NotePlease note that:An unexpected abort of the server during a transaction, caused by a hardwarefailure or power cut, will probably lead to an inconsistent database state if a transaction was active at the shutdown time. So we advise to usethe [[Commands#BACKUP|BACKUP]] command to backup your database regularly. If the worst case occurs, you can try the [[Commands#INSPECT|INSPECT]] command to check if your database has obvious inconsistencies, and [[Commands#RESTORE|RESTORE]] to restore a previous version of the database.

* Locks ''cannot be synchronized'' across BaseX instances that run in different JVMs. If concurrent write operations are to be performed, we generally recommend working with the client/server or the HTTP architecture .* An ''unexpected abort'' of the server during a transaction, caused by a hardware failure or power cut, may lead to an inconsistent database state if a transaction was active at shutdown time. So it is advisable to use the [[Commands#CREATE BACKUP|BACKUP]] command to regularly backup your database. If the worst case occurs, you can try the [[Commands#INSPECT|INSPECT]] command to check if your database has obvious inconsistencies, and use [[Commands#RESTORE|RESTORE]] to restore the last backed up version of the database. ==XQuery Update Transactions==

BaseX 7provides support for multiple read and single write operations (using preclaiming and starvation-free two phase locking). This means that: * Read transactions are executed in parallel.* If an updating transaction comes in, it will be queued and executed after all previous read transaction have been executed.6 introduces locking * Subsequent operations (read or write) will be queued until the updating transaction has completed. Each database has its own queue: An update on database level. Writing transactions do A will not necessarily block all other transactions any moreoperations on database B. This is under the premise that it can be statically determined, i.e., before the transaction is evaluated, which databases will be accessed by a transaction (see [[#Limitations|below]]). The number of maximum parallel transactions can be limited by setting adjusted with the [[Options#PARALLEL|PARALLEL]] option. With {{Version|8.6}}, locking has been improved: * Jobs without database access will never be locked. Globally locking jobs can now be executed in parallel with non-locking jobs.* A {{Option|FAIRLOCK}} option has been added: By default, read transactions will now be favored, and transactions that access no databases can be evaluated even if the transactions limit has been reached. ==External Side Effects==

Deadlocks are prevented Custom locks can be acquired by using preclaiming two phase locking. Execution is starvationsetting the BaseX-specific XQuery options {{Code|query:read-lock}} and {{Code|query:write-free as lock aquiration is queued per database}}. Due to Multiple option declarations may occur in the specifics prolog of XQuery Updatea query, all updates but multiple values can also be separated with commas in a single declaration. These locks are written at in another namespace than the end of database names: the query. Locking is strict with the exception that databases for which BaseX recognizes it lock value {{Code|factbook}} will not write to are downgraded to read lockslock a database named factbook.

These option declarations will put read locks on ''foo'', ''bar'' and ''batz'' and a write lock on ''quix'': <pre class="brush:xquery">declare option query:read-lock "foo,bar";declare option query:read-lock "batz";declare option query:write-lock "quix";</pre> ===Java Modules=== Locks can also be acquired on [[Java Bindings#Locking|Java functions]] which are not synchronized between multiple BaseX instancesimported and invoked from an XQuery expression. We generally recommend working with the client/server architecture if concurrent It is advisable to explicitly lock Java code whenever it performs sensitive read and write operations are to be performed.

The current identification of which databases to lock is limited to [[Database locking works with all commands]] using no unless the glob syntax and queries that access is used, such as in the currently opened database, XQuery functions that explicitly specify a database, and expressions that address no database at all.following command call:

Some examples on database-locking enabled commands* {{Code|DROP DB new*}}:drop all databases starting with "new"

Some examples on databaseDeciding which databases will be accessed by a complex XQuery expression is a non-locking enabled trivial task. Database detection works for the following types of queries:

All of these queries can databases will be executed in parallel: Some examples on locked by queries that are not supported by database-locking yet: * <code>let $db := 'factbook' return doc($db)</code>, will read lock globally: referencing database names isn’t supported yet* {{Code|for $db in ('factbook') return doc($db)}}, will read lock globally: ditto* {{Code|doc(doc('test')/reference/text())}}, will read lock globally: ditto* <code>let $db := 'test' return insert nodes <test/> into doc($db)</code>, will write lock globallyof the following kind: ditto

==How to disable== In order to enable traditional process locking, You can consult the query info output (which you find in the [[GUI#Visualizations|Info View]] of the option GUI or which you can turn on by setting <code>[[Options#GLOBALLOCKINGQUERYINFO|GLOBALLOCKINGQUERYINFO]]</code> can be set to {{Code|true}}. This can e.g. be done ) to find out which databases have been locked by editing your {{Code|.basex}} file (see [[Options]] for more details)a query.

During the term of a database update, a locking file {{Code|upd.basex}} will reside in that database directory. If the update fails for some unexpected reason, or if the process is killed ungracefully, this file may will not be deleted. In this case, the database cannot be opened anymore using the default commands, and the message "Database ... is being updated, or update was not completed" will be shown instead.  If the locking file is manually removed, you may be able to reopen the database, but you should be aware that database may have got corrupt due to the interrupted update process, and you should revert to the most recent database backup.

To avoid database corruptions that are caused by accidental write operations running in from different JVMs, a shared lock is requested on the database table file ({{Code|tbl.basex}}) whenever a database is opened. If an update operation is triggered, and if no exclusive lock can be acquired, it will be rejected with the message "Database ... is currently opened by another process." if no exclusive lock can be acquired.

As the standalone versions of BaseX (command-linePlease note that you cannot 100% rely on this mechanism, GUI) cannot as it is not possible to synchronize operations across different JVMs. You will be synchronized with other BaseX instances, we generally recommend working with safe when using the client/server or HTTP architecture if concurrent write operations are to be performed.

 * Added: database locking introduced, replacing process locking.

 * Updated: pin files replaced with shared/exclusive filesystem locking.

 * Added: pin files to mark open databases.

 * Added: update lock files [[Category:Server]][[Category:Internals]].