[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-1967) Incorrect join formed when for one-to-one relationship to subclass in a mixed table/class table/subclass mapping strategy

[Sunil Prakash Inteti (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=31599#action_31599 ] 

Sunil Prakash Inteti commented on HHH-1967:
-------------------------------------------

This blog throws light on this issue.
http://blog.xebia.com/2008/10/21/confusing-hibernate-configuration-syntax/

> Incorrect join formed when for one-to-one relationship to subclass in a mixed table/class table/subclass mapping strategy
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HHH-1967
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1967
>             Project: Hibernate Core
>          Issue Type: Bug
>    Affects Versions: 3.2.0.cr2
>         Environment: Hibernate 3.1/3.2 Sybase
>            Reporter: Bill Swayze
>
> I have an inheritance hierarchy that I am trying to implement using the table per class and table per subclass mix strategy.  A particular subclass (joined) has a unique foreign key one-to-one (mapped as many-to-one per documentation) association with another class.  The sql joins generated are being formed with the base class table alias name and the subclass's column name resulting in invalid column name errors from the database.  There doesn't appear to be anything in the code to discriminate whether the associations are to base or the subclass.

-- 
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