2990 2006-03-07 10:11:38 +0000 [Update] Possible inconsistency in compatibility of update primitives 2006-06-23 09:52:30 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Update Facility Working drafts All Windows 2000 CLOSED FIXED P2 normal --- 1 avyas andrew.eisenberg public-qt-comments oldest_to_newest 8614 0 avyas 2006-03-07 10:11:38 +0000 The current compatibility table invalidates certain possibilities of update primitives when the target node is the same. Apart from the equality relation between the target nodes, parent relationship among the target nodes of certain primitives operations can also create problems (one which compatibility table wants to avoid). For e.g. should insAft(t1, r1) be incompatible with insAsLast(t2, r2) and insInto(t2, r2) if t1 is the last child of t2. 10210 1 chamberl 2006-06-23 09:52:05 +0000 Avinash, This issue has been overtaken by some changes to the compatibility rules. The rules will no longer be described by a table of conflicts between primitives, but by a simpler set of rules at the expression level. The specific example in this comment will not be considered a conflict. Precedence rules will be provided to make the outcome deterministic. In the example, the outcome will be that r1 will be immediately after t1, and r2 will be the last child of t2. The new rules will be published within the next few days in a new working draft. Since the old compatibility table is gone, I have closed this comment. When you see the new working draft, if you are not satisfied with the resolution of your issue, please open a new Bugzilla comment. Regards, Don Chamberlin (for the Query Working Group)