[CAY-615] Delete Rule Cascade with Deny on reverse relationship always fails.

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 1.2 branch
• Fix Version/s: Undefined future
• Component/s: Core Library
• Assignee: Mike Kienenberger
• Reporter: Mike Kienenberger
• Created: 28/Jul/06 17:55
• Updated: 24/Sep/13 20:28
• Resolved: 24/Sep/13 20:28

Description

Delete Rule Cascade with Deny on reverse relationship always fails.

On 7/27/06, Mike Kienenberger <[e-mail]> wrote:
> Does the Deny still happen if the only
> reverse-relationship value is the cascading original object to be
> deleted?

On 7/27/06, Andrus Adamchik <[e-mail]> wrote:
> Doesn't look like DataContextDeleteAction is smart about it:
>
> if (relatedObjects.size() == 0)

{ > continue; > }

>
> // process DENY rule first...
> if (relationship.getDeleteRule() == DeleteRule.DENY)

{ > object.setPersistenceState(oldState); > > String message = relatedObjects.size() == 1 > ? "1 related object" > : relatedObjects.size() + " related objects"; > throw new DeleteDenyException(object, > relationship.getName(), message); > }

>
> To handle cascade/deny combination we may need to change this code to
> check that at least one object in 'relatedObjects' collection is
> itself not deleted.