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

[Bug 5340] [UPD] Atomicity is untestable

From: <bugzilla@wiggum.w3.org>
Date: Tue, 08 Jan 2008 19:06:26 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1JCJmM-0000rK-Qa@wiggum.w3.org>

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





------- Comment #3 from zhen.liu@oracle.com  2008-01-08 19:06 -------
I think that the 'update atomcity' and 'testablity of it' are two orthorgonal
issues. I agree that the 'testability' is an issue. Of course, testing using
deep-equal() is not bullet proof. However, 'testability'
should NOT affect the rule of 'update atomicity' in the spec. 

I agree that for some in memory implemetations, it is very costly to guarantee
atomicity whereas for DB based implementation, it is natural given the
transaction capability in DB.  However, given the fact that XQuery can be
widely
implemented  in both DB and mid-tier in memory processor, 
it is probably better to give
an implementation a configurable choice to state if they can guarantee such
atomicity.
Received on Tuesday, 8 January 2008 19:06:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:14:49 GMT