Bug 188 : Reverse Bug 174 behaviour ... save for ManyToMany will save relationship without requiring Cascade.ALL etc
Priority 
High
Reported Version 
 
Logged By 
Rob
Status 
Fixed
Fixed Version 
2.3.0
Assigned To 
 
Product 
Ebean - core
Duplicate Of 
 
Created 
03/12/2009
Updated 
03/12/2009
Type 
Bug
 
Attachments 
No attachments

There is a problem with the change made with Bug 174.

Specifically, if there are additions on both sides of a ManyToMany ... then the relationship can easily end up being inserted twice - ending in a constraint violation.

The suggestion is to revert the behaviour back so that a ManyToMany requires Cascade.SAVE before the relationships are saved.

 
Rob 03 Dec 07:56
Fixed in HEAD

Fixed in HEAD. Put the behaviour back... so now Cascade.SAVE is required for the ManyToMany relationships (inserts/deletes from intersection table) to occur.

woResponse

Upload a file