[Hibernate-issues] [Hibernate-JIRA] Updated: (HHH-294) implicit join in both subselect and outer query : single join

[<no...@at...>]

The following issue has been updated:

    Updater: Steve Ebersole (mailto:st...@hi...)
       Date: Tue, 12 Apr 2005 8:44 PM
    Changes:
             Fix Version changed to 3.0.2
             Fix Version changed from 3.0.1
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://opensource.atlassian.com/projects/hibernate/browse/HHH-294?page=history

---------------------------------------------------------------------
View the issue:
  http://opensource.atlassian.com/projects/hibernate/browse/HHH-294

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HHH-294
    Summary: implicit join in both subselect and outer query : single join
       Type: Improvement

     Status: Open
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: Hibernate3
   Fix Fors:
             3.0.2

   Assignee: Steve Ebersole
   Reporter: Steve Ebersole

    Created: Thu, 31 Mar 2005 9:14 AM
    Updated: Tue, 12 Apr 2005 8:44 PM

Description:
See HHH-280 for the details.

Basically, that was fixed by reverting to the old parser output of generating duplicate joins.  This should be fixed to use the same join both times for effeciency.

There were a number of ways we might acheive this:
1) Somehow suspend processing of subqueries until their containing query is completely processed.  The trick here is that the join definition from the outer query would already have been resolved when processing the inner query resumes at which point we could simply reuse the join def from the outer query (this is the same thing as putting the implicit join in the outer query *before* the subquery, which works).  This approach (while simple in its concept) seems very difficult to acheive with the ANTLR parser.
2) Perform some post processing sort of like we do with the "join post processing".  Yuck!
3) When attempting to resolve the DotNode (representing the implicit join) take a peek at "child from clauses" to see if any of them defined the same "implicit join path"; if so "promote" that join fragment from the child FromClause to the current FromClause.

I will attempt #3.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira