Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Cannot Reproduce
-
Affects Version/s: 2.0-BETA4
-
Fix Version/s: None
-
Component/s: ORM
-
Security Level: All
-
Labels:None
Description
When merging some cascade merge object-graphs, the same entity in a ManyToMany association can be put into a collection twice during doMerge.
The attached patch should stop this from happening.
Activity
Dave Keen
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Attachment | multipleaddmerge2.diff [ 10897 ] |
Alexander
made changes -
| Status | Open [ 1 ] | Closed [ 6 ] |
| Resolution | Cannot Reproduce [ 5 ] |
Benjamin Eberlei
made changes -
| Workflow | jira [ 12094 ] | jira-feedback [ 15660 ] |
Benjamin Eberlei
made changes -
| Workflow | jira-feedback [ 15660 ] | jira-feedback2 [ 17524 ] |
Benjamin Eberlei
made changes -
| Workflow | jira-feedback2 [ 17524 ] | jira-feedback3 [ 19781 ] |
This list may be incomplete, as errors occurred whilst retrieving source from linked applications:
- Request to http://www.doctrine-project.org/fisheye/ failed: Error in remote call to 'FishEye 0 (http://www.doctrine-project.org/fisheye/)' (http://www.doctrine-project.org/fisheye) [AbstractRestCommand{path='/rest-service-fe/search-v1/crossRepositoryQuery', params={query=DDC-875, expand=changesets[-21:-1].revisions[0:29],reviews}, methodType=GET}] : Received status code 503 (Service Temporarily Unavailable)
which conditions lead to this problem? I want to write a test for it