|
Berkeley DB XML version 2.4.16 |
|||||||||
PREV NEXT | FRAMES NO FRAMES |
Deprecated Classes | |
---|---|
com.sleepycat.dbxml.XmlModify
As of release 2.4.x, replaced by direct use of XQuery Update. The XmlModify object and its methods are deprecated and will be dropped in some future release. XQuery Update syntax should be used for both in-place, and copy-based modifications. It is both simpler and more efficient. The context within which a set of one or more documents specified by an XQuery query can be modified in place. The modification is performed using an XmlModify object, and a series of methods off that object that identify how the document is to be modified. Using these methods, the modification steps are identified. When the object is executed, these steps are performed in the order that they were specified.
XmlModify objects are created using
The modification steps are executed against one or more documents using
Document modifications are always written back to their respective containers. If this behavior is not desired, it is necessary to copy a document to a temporary location and modify it there. Documents in containers using node storage are updated partially, and only affected nodes and indexes are modified, if possible. Documents in containers using whole-document storage are entirely rewritten and re-indexed. During construction, XmlModify objects are not free-threaded. They must be constructed in a thread-safe manner. However, a single XmlModify object, once constructed, can be used simultaneously by multiple threads. |
Deprecated Fields | |
---|---|
com.sleepycat.db.LockMode.DEGREE_2
|
|
com.sleepycat.db.CursorConfig.DEGREE_2
|
|
com.sleepycat.db.LockMode.DIRTY_READ
|
|
com.sleepycat.db.CursorConfig.DIRTY_READ
|
|
Berkeley DB XML version 2.4.16 |
|||||||||
PREV NEXT | FRAMES NO FRAMES |