[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-5189) Same table is mapped twice but different primary keys. Giving error while secondPassCompileForeignKeys.

[Gail Badner (JIRA)]

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

Gail Badner commented on HHH-5189:
----------------------------------

Does this happen using 3.5.1?

If so, please check to see if it is already an unresolved issue reported for 3.5.x:
http://opensource.atlassian.com/projects/hibernate/secure/IssueNavigator.jspa?mode=hide&requestId=11080

To see if it has been fixed for the next 3.5.x release:
http://opensource.atlassian.com/projects/hibernate/secure/IssueNavigator.jspa?mode=hide&requestId=11081

If this is still an issue in 3.5.1, then please attach a unit test that reproduces your issue. You may find an existing unit test to get you started in testsuite.

Thanks,
Gail


> Same table is mapped twice but different primary keys. Giving error while secondPassCompileForeignKeys.
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HHH-5189
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5189
>             Project: Hibernate Core
>          Issue Type: Bug
>         Environment: OS: Linux
> DB : Oracle
> Hibernate Version : 3.2.5 ga
>            Reporter: Sardar Romender Singh
>            Priority: Trivial
>
> Two tables are mapped with different primary keys. 
> Example :
> I have customer table which is mapped to Customer Entity whose primary keys are Customer id and status (which says authorized customer or un authorized customer). 
> I have one more entity mapped to same table CustomerLight which will load only some specific fields of the customer which contains the where clause which specifies to load only authorized customer.
> There are some more entities which are mapped to customer entity with key-many-to-one relationship.
> After loading of the mapping file while validation of foriegn key constraints its failing 
> Foreign key constraint failed "must have same number of columns as the referenced primary key"
> This is happening only in some environments not all.

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