| Summary: | Aggregate functions fail because wrong code is generated for entities/tables joined twice | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Karsten Wutzke <kwutzke> |
| Component: | Eclipselink | Assignee: | James Sutherland <jamesssss> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | blocker | ||
| Priority: | P2 | CC: | dapatel, eclipselink.orm-inbox, jamesssss, kwutzke, michael.f.obrien, SteliyanPGeorgiev, tom.ware |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| URL: | http://www.eclipse.org/forums/index.php?t=msg&th=201436 | ||
| Whiteboard: | |||
|
Description
Karsten Wutzke
Don't try to debug this using HSQLDB 2.0.0. This version has a bug that relates to this issue: http://stackoverflow.com/questions/4376703/hibernate-jpql-hql-bug-with-aggregate-functions-showing-results-of-wrong-table-e I've repacked the SSCCE with HSQLDB 2.0.1-rc2 (link) Workaround: Run two queries, one for sf and one for sa. Setting target and priority. See the following page for the meanings of these fields: http://wiki.eclipse.org/EclipseLink/Development/Bugs/Guidelines Will this be fixed anytime soon? To me appears to be one of the easier bugs to fix. I encourage anyone in the community for whom this bug is an issue to vote for it. Votes are one of the main criteria we use to determine which bugs to fix. Hi, If you are a software tester or a QA engineer then you must be thinking every minute to find a bug in an application. And you should be! I think finding a blocker bug like any system crash is often rewarding! No I don’t think like that. we should try to find out the bugs that are most difficult to find and those always misleads users.... SQA serviceshttp://testing-whiz.com/ This seems to have been fixed in 2.4. At least the aliases are now correct. The result is the same I think, this is because of how joins work, so I think the original query will not work as the user seems to expect no matter what alias is used. Added a test case to the complex JPQL test suite. The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |