Hi, On Nov 29, 2007 9:49 AM, Eugeny N Dzhurinsky <[EMAIL PROTECTED]> wrote: > May be there is something we can do to relax repository when deletion > operations occur?
Instead of doing a single large delete operation, you could try deleting each node or subtree separately. All nodes that are being deleted are loaded into the transient space (in memory) of a session and the entire change-set is checked for violations of referential integrity and other constraints before the changes are persisted. Currently this operation blocks all other (uncached) access to the repository, so it's normally better to split large deletes (or imports, etc.) to smaller parts if you want to keep concurrently accessing the repository. BR, Jukka Zitting
