| Summary: | DeleteAllQuery ignores additional join expression in multitable case | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Andrei Ilitchev <andrei.ilitchev> | ||||
| Component: | Eclipselink | Assignee: | Nobody - feel free to take it <nobody> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | ||||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Andrei Ilitchev
Created attachment 197269 [details]
Suggested patch.
Fixed the problem by allowing DeleteAll query to substitute usage of
queryManager.getAdditionalJoinExpression();
for
queryManager.getMultipleTableJoinExpression();
when NOT EXIST subquery is created.
Also added EntityManagerJUnitTestSuite.deleteAllProjects to confirm that the fix didn't break no where clause case when inheritance is involved.
The patch checked into trunk. Completed: At revision: 9501 The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |