Subject:Berkeley DB XML integration Author:(Deleted User) Date:17 Jul 2006 10:52 AM
Paul,
Our model allows you to browse your entire file system and access (read-only) any .dbxml container whether or not it is in a database environment.
If the container you select happens to be in a database environment listed in the BerkeleyDBXML file, then we will allow read/write access to the container.
Subject:Berkeley DB XML integration Author:(Deleted User) Date:17 Jul 2006 11:35 AM
Paul,
I'd like to troubleshoot this off line.
Can you please send a email to stylus-field-report?
Let us know which version of dbxml you are using.
If the files are not too large, can you attach copies of them?
Subject:Berkeley DB XML integration Author:(Deleted User) Date:19 Jul 2006 10:19 AM
For the record, Paul's Berkeley DB was created with transactions enabled, but locking disabled. Any attempt to update containers in this situation
will generate the error message from the Berkeley DB XML system.
com.stylusstudio.sleepycat.dbxml.DBXMLException: Cannot write...
...
...
DBcursor->get: the DB_DIRTY_READ, DB_DEGREE_2 and DB_RMW flags require locking.
To cure the problem, it is necessary to recreate the database with both
transactions and locking enabled.