Thread: [Hibernate-issues] [Hibernate-JIRA] Created: (HHH-1499) use subselect fetching for collection join f

An object relational-mapping (ORM) library for Java

hibernate-issues

[Hibernate-issues] [Hibernate-JIRA] Created: (HHH-1499) use subselect fetching for collection join fetches with DISTINCT or firstResult/maxRows

From: Steve E. (JIRA) <no...@at...> - 2006-02-16 19:45:12

use subselect fetching for collection join fetches with DISTINCT or firstResult/maxRows
---------------------------------------------------------------------------------------

         Key: HHH-1499
         URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1499
     Project: Hibernate3
        Type: Improvement

  Components: query-hql  
    Reporter: Steve Ebersole
 Assigned to: Steve Ebersole 
     Fix For: 3.2.0


As a follow on to HHH-1411and HHH-1412...

Both of those above were actually resolved by handling the DISTINCT-ion and/or firstResult/maxRows *in memory*.  A better solution is to not honor the join fetch in these cases, perform the requested operation, and then get the requested join fectehd collections through subselect fetches.  

As is, this would work as long as the collections have subselect fetching enabled in metadata, but would actually use immediate fetching (n+1) for any collections not defining subselect fetching in metadata.  This is due to the way PersistenceContext.initializeNonLazyCollections() currently works.

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Updated: (HHH-1499) use subselect fetching for collection join fetches with DISTINCT or firstResult/maxRows

From: Steve E. (JIRA) <no...@at...> - 2006-03-16 15:38:17

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1499?page=all ]

Steve Ebersole updated HHH-1499:
--------------------------------

    Fix Version:     (was: 3.2.0.alpha2)
                 3.2.0

> use subselect fetching for collection join fetches with DISTINCT or firstResult/maxRows
> ---------------------------------------------------------------------------------------
>
>          Key: HHH-1499
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1499
>      Project: Hibernate3
>         Type: Improvement

>   Components: query-hql
>     Reporter: Steve Ebersole
>     Assignee: Steve Ebersole
>      Fix For: 3.2.0

>
>
> As a follow on to HHH-1411and HHH-1412...
> Both of those above were actually resolved by handling the DISTINCT-ion and/or firstResult/maxRows *in memory*.  A better solution is to not honor the join fetch in these cases, perform the requested operation, and then get the requested join fectehd collections through subselect fetches.  
> As is, this would work as long as the collections have subselect fetching enabled in metadata, but would actually use immediate fetching (n+1) for any collections not defining subselect fetching in metadata.  This is due to the way PersistenceContext.initializeNonLazyCollections() currently works.

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Updated: (HHH-1499) use subselect fetching for collection join fetches with DISTINCT or firstResult/maxRows

From: Steve E. (JIRA) <no...@at...> - 2006-03-27 17:36:30

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1499?page=all ]

Steve Ebersole updated HHH-1499:
--------------------------------

    Fix Version: 3.2.0
                     (was: 3.2.0 cr1)

> use subselect fetching for collection join fetches with DISTINCT or firstResult/maxRows
> ---------------------------------------------------------------------------------------
>
>          Key: HHH-1499
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1499
>      Project: Hibernate3
>         Type: Improvement

>   Components: query-hql
>     Reporter: Steve Ebersole
>     Assignee: Steve Ebersole
>      Fix For: 3.2.0

>
>
> As a follow on to HHH-1411and HHH-1412...
> Both of those above were actually resolved by handling the DISTINCT-ion and/or firstResult/maxRows *in memory*.  A better solution is to not honor the join fetch in these cases, perform the requested operation, and then get the requested join fectehd collections through subselect fetches.  
> As is, this would work as long as the collections have subselect fetching enabled in metadata, but would actually use immediate fetching (n+1) for any collections not defining subselect fetching in metadata.  This is due to the way PersistenceContext.initializeNonLazyCollections() currently works.

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Updated: (HHH-1499) use subselect fetching for collection join fetches with DISTINCT or firstResult/maxRows

From: Steve E. (JIRA) <no...@at...> - 2006-05-06 04:36:26

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1499?page=all ]

Steve Ebersole updated HHH-1499:
--------------------------------

    Fix Version: 3.2.0
                     (was: 3.2.0.cr2)

> use subselect fetching for collection join fetches with DISTINCT or firstResult/maxRows
> ---------------------------------------------------------------------------------------
>
>          Key: HHH-1499
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1499
>      Project: Hibernate3
>         Type: Improvement

>   Components: query-hql
>     Reporter: Steve Ebersole
>     Assignee: Steve Ebersole
>      Fix For: 3.2.0

>
>
> As a follow on to HHH-1411and HHH-1412...
> Both of those above were actually resolved by handling the DISTINCT-ion and/or firstResult/maxRows *in memory*.  A better solution is to not honor the join fetch in these cases, perform the requested operation, and then get the requested join fectehd collections through subselect fetches.  
> As is, this would work as long as the collections have subselect fetching enabled in metadata, but would actually use immediate fetching (n+1) for any collections not defining subselect fetching in metadata.  This is due to the way PersistenceContext.initializeNonLazyCollections() currently works.

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Updated: (HHH-1499) use subselect fetching for collection join fetches with DISTINCT or firstResult/maxRows

From: Steve E. (JIRA) <no...@at...> - 2006-06-28 16:44:18

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1499?page=all ]

Steve Ebersole updated HHH-1499:
--------------------------------

    Fix Version: 3.2.1
                     (was: 3.2.0.cr3)

> use subselect fetching for collection join fetches with DISTINCT or firstResult/maxRows
> ---------------------------------------------------------------------------------------
>
>          Key: HHH-1499
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1499
>      Project: Hibernate3
>         Type: Improvement

>   Components: query-hql
>     Reporter: Steve Ebersole
>     Assignee: Steve Ebersole
>      Fix For: 3.2.1

>
>
> As a follow on to HHH-1411and HHH-1412...
> Both of those above were actually resolved by handling the DISTINCT-ion and/or firstResult/maxRows *in memory*.  A better solution is to not honor the join fetch in these cases, perform the requested operation, and then get the requested join fectehd collections through subselect fetches.  
> As is, this would work as long as the collections have subselect fetching enabled in metadata, but would actually use immediate fetching (n+1) for any collections not defining subselect fetching in metadata.  This is due to the way PersistenceContext.initializeNonLazyCollections() currently works.

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira