[Bug 2990] [Update] Possible inconsistency in compatibility of update primitives


chamberl@almaden.ibm.com changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

------- Comment #1 from chamberl@almaden.ibm.com  2006-06-23 09:52 -------
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.
Don Chamberlin (for the Query Working Group)

Received on Friday, 23 June 2006 09:52:15 UTC