[INFOD-WG] More on ExecutionMode for DROP

[Dieter Gawlick]

The reference implementation shows that we have to clarify the 
ExecutionMode in DROP.:

Lets us assume that the request is to DROP an entry we some property 
instances referencing this entry. We should drop that entry and all the 
property instances referencing it in all cases - otherwise the drop 
logic is somewhat strange.

"DISABLE NEW' would ignore this entry, it is in the solution set of the 
newly defined constraint; it remains in the solution set of existing 
constraints.

"CASCADE" is not needed any longer, we just remove the entry.

This makes the implementation much easier

Dieter
-- 

Oracle Email Signature Logo
Dieter Gawlick | Architect | 650.506.8706
Oracle Server Technologies
500 Oracle Parkway | Redwood Shores, CA 94065
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.ogf.org/pipermail/infod-wg/attachments/20070716/370fbe15/attachment.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 658 bytes
Desc: not available
Url : http://www.ogf.org/pipermail/infod-wg/attachments/20070716/370fbe15/attachment.gif