Hi Buddy on web,
For all your questions, I can probably give you a short answer: you will need to use the client/server architecture of BaseX if you want to concurrently read and update one database. For general information on our transaction management, you could have a look at our Wiki article [1].
Hope this helps, Christian
[1] http://docs.basex.org/wiki/Transaction_Management
On Thu, Dec 3, 2015 at 9:18 PM, buddyonweb-software@yahoo.com wrote:
I have a Java process that continually scans for incoming .xml files deposited into a system folder on the OS. When it finds a file (say a.xml), it will create a DB for that file (call it DB-A) and load the XML file into that database (DB-A). Note: DB names will be guaranteed to be unique when created, so there will never be 2 DB-A databases created.
As this file is processed by a seondar, other XML files will be added into DB-A - but all documents will relate only to the processing of the a.xml file (for example, various statistics, etc.).
Now, there is a secondary/separate java process, that scans the database instances that have been created with the XML file loaded. This secondary process does some querying on that file and adds additional XML documents to that database. That is only this process will add new documents to the database.
So my question is this:
- With process 1 creating and inserting the original .xml file, is there a
chance for database contention or is this architecture pretty safe from contention? Note: both Java process are simply using the BaseX.jar file.
- If I added a third Java process in the future, that would a) only access
existing documents in read only mode b) could add new documents to the database that no other process would read or update, is this safe from contention?
Thanks in advance.