From: Adam R. <ada...@de...> - 2007-11-20 10:37:56
|
eXists locking internally will take care of all resources and concurrent = modifications. For an XUpdate many updates may happen in a single = transaction, for XQuery Update Extensions normally each update is a = transaction, however I did add a pragma that will allow you to batch = many XQuery Updates into a single transaction to help improve atomicity = where appropriate. -----Original Message----- From: exi...@li... on behalf of WISE, Jon Sent: Mon 19/11/2007 16:50 To: exi...@li... Subject: Re: [Exist-open] Design question on collections and documents =20 My reference to 'recreating the XML document' was based on my mistaken view of the update operation which saw an XML document as the unit of storage. Looking at the JavaDocs for the first time I can see DOM classes and so I guess an XUPdate is a fairly efficient operation. I should have read more before going to print but this does raise another issue in that if an update is to only part of a document and one logical change requires more than one update, a transaction would be needed but is not yet available. Is there any discussion as to how a design should proceed when there might be several asynchronous processes issuing updates?=20 Jon Wise - This email is confidential to the intended recipient. If you have = received it in error please notify the sender and delete it from your = computer. The University of Gloucestershire is a company limited by guarantee = registered in England and Wales. Registered number: 06023243. = Registered office: The Park, Cheltenham, GL50 2RH - -------------------------------------------------------------------------= This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Exist-open mailing list Exi...@li... https://lists.sourceforge.net/lists/listinfo/exist-open |