[nhibernate-issues] [JIRA] Updated: (NH-517) Unnecessary selects when mapped as class instead of column

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-517?page=all ]

Sergey Koshcheyev updated NH-517:
---------------------------------

    Fix Version: LATER

> Unnecessary selects when mapped as class instead of column
> ----------------------------------------------------------
>
>          Key: NH-517
>          URL: http://jira.nhibernate.org/browse/NH-517
>      Project: NHibernate
>         Type: Improvement
>   Components: Core
>     Versions: 1.0.1
>     Reporter: Ruurd Boeke
>      Fix For: LATER
>  Attachments: NH517.rar
>
> I've delved deeper into the problem described by: http://jira.nhibernate.org/browse/NH-435
> It seems I have the same kind of problem, but it has nothing to do with using an outer select.
> Short summary: I'm getting N selects when I have mapped a one-to-many relation, and in the many-side, the composite-ID maps towards the 'one' with a key-many-to-one instead of a key-property.
> This means that nHibernate is using one well-constructed query to get all the info it needs, and then sends a SELECT for every row it got back like this: select parentID from parents where parentID = :parentid
> In my current situation, this leads to several thousands of selects.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira