W3C home > Mailing lists > Public > www-ql@w3.org > January to March 2006

RE: XQuery Update - unordered collection of update primitives

From: Michael Rys <mrys@microsoft.com>
Date: Mon, 30 Jan 2006 06:09:58 -0800
Message-ID: <BAE415CEAA831548800F68C44E905AF5047336C6@RED-MSG-60.redmond.corp.microsoft.com>
To: "TAN Kuan Hui" <kuanhui@xemantics.com>, "Jonathan Robie" <jonathan.robie@datadirect.com>, <www-ql@w3.org>

The updating integrity is guaranteed by the commutability constraints
(only operations considered to be commutable are allowed). The reason
you want an unordered collection is that you can perform your updates
efficiently and potentially in parallel.

Best regards
Michael

> -----Original Message-----
> From: www-ql-request@w3.org [mailto:www-ql-request@w3.org] On 
> Behalf Of TAN Kuan Hui
> Sent: Monday, January 30, 2006 5:07 AM
> To: Jonathan Robie; www-ql@w3.org
> Subject: XQuery Update - unordered collection of update primitives
> 
> 
> Section 2.1, Extensions to the Processing Model, carries the following
> definition.
> 
> [Definition: A pending update list is an unordered collection 
> of update primitives, which represent node state changes that have not
> yet been applied.]
> 
> What is the significance of an <<unordered>> collection of 
> update primitives ?
> How is updating integrity preserved with an unordered 
> collection of update
> instructions ? I could not find an explicit description on 
> the above and
> would appreciate clarifications.
> 
> Thank you.
> 
> Kuan Hui
> 
> 
> 
> 
> 
> 
Received on Monday, 30 January 2006 14:10:43 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:43:44 UTC