[Hibernate-issues] [Hibernate-JIRA] Commented: (HHH-1939) Extended support for mixing table-per-subclass and table-per-hierarchy

[Steve E. (JIRA) <no...@at...>]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1939?page=comments#action_23761 ] 

Steve Ebersole commented on HHH-1939:
-------------------------------------

Here is a good place to start:
http://fisheye.jboss.com/viewrep/Hibernate/trunk/Hibernate3/src/org/hibernate/persister/entity

Have a look at:
1) AbstractEntityPersister
2) JoinedSubclassEntityPersister
3) SingleTableEntityPersister

> Extended support for mixing table-per-subclass and table-per-hierarchy
> ----------------------------------------------------------------------
>
>          Key: HHH-1939
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1939
>      Project: Hibernate3
>         Type: Improvement

>   Components: core
>     Versions: 3.1.3
>  Environment: Hibernate 3.1.3, Postgresql 8.1
>     Reporter: Jason Bennett

>
>
> http://forum.hibernate.org/viewtopic.php?t=962067
> At present, Hibernate allows limited mixing of table-per-hierarchy and table-per-subclass. Specifically, once a particular inheritance branch begins using TPS, it cannot switch back to TPH.
> In our domain (as described in the above forum post), we have several fine-grained objects near the top of our hierarchy, with some bulkier objects lower down. What we would like to do is to run TPS for the higher, smaller classes (where we have referential integrity reasons to break them out), and then switch back to table-per-hierarchy further down, where the majority of our queries are run.
> I would be happy to assist in implementation, given some direction.

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