W3C home > Mailing lists > Public > public-qt-comments@w3.org > January 2007

[Bug 4168] [UPD] Atomicity is a problem for a non-transacted implementation

From: <bugzilla@wiggum.w3.org>
Date: Mon, 29 Jan 2007 22:42:26 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1HBfCk-0003x2-Ri@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=4168


chamberl@almaden.ibm.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX




------- Comment #2 from chamberl@almaden.ibm.com  2007-01-29 22:42 -------
John,
Thanks for your comment, which was discussed by the Query Working Group on
January 29, 2007. The working group feels that it is important to define atomic
semantics for updates to an XDM instance. However, it is not our intention to
specify semantics for how these updates are propagated to an underlying
persistent store. Furthermore, the atomic property of updates to an XDM
instance are defined only for errors that are defined in the XQuery
specification (for example, they do not apply to undefined circumstances such
as power failures or running out of memory.) We will add text to the Update
specification clarifying the circumstances in which atomicity is required, as
suggested in Comment #1 by Michael Kay. However, since this resolution is not
exactly what you suggested, we are marking this bug report as "Won't Fix." If
you are satisfied with this resolution, please change its status to "Closed."

Regards,
Don Chamberlin (for the Query Working Group)
Received on Monday, 29 January 2007 22:42:35 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:32 UTC