[Hibernate-JIRA] Commented: (HHH-1233) Allow mixing <union-subclass>and <subclass>
by Steve Ebersole (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1233?page=c... ]
Steve Ebersole commented on HHH-1233:
-------------------------------------
14th? Holy cow, better get right on that! LOL.
> Allow mixing <union-subclass>and <subclass>
> -------------------------------------------
>
> Key: HHH-1233
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1233
> Project: Hibernate3
> Issue Type: Improvement
> Components: core
> Environment: N/A
> Reporter: Gunther Schadow
>
> BACKGROUND:
> Hibernate allows mixing <subclass> and <joined-subclass> inheritance mappings but apparently not <subclass> and <union-subclass> mappings, however, this seems like the most useful combination. Example:
> USE CASE:
> We may have a hierarchy with very unevenly distributed mass, i.e., some subclasses have millions of objects, others have only a half-dozen. There may be a lot of different subclasses of the smaller sort.
> Union-subclass seems ideal to work with a dozen different humongous tables, as they can be placed on different tablespaces and managed differently. However, for the 200 or so subclasses whith only a dozen objects each, it would be easier to map these into a single table per sub-hierarchy.
> REQUESTED FEATURE:
> Therefore it seems fair to suggest that <subclass> mappings should be supported underneath <union-subclass> mappings. To allow that the <discriminator> element would have to be handled inside a <union-subclass> element and same for the discriminator-value attribute. Perhaps one could limit the complexity by requiring that the outer mapping must be union-subclass and the inner can be subclass but not vica versa?
> WORKAROUNDS:
> As the documentation mentions one could just create several independent <class> hierarchies, thus effectively emulating the first level of union-subclass specializations. But that would not allow specifying polymorphic associations.
> ESTIMATED EFFORT:
> It could be difficult to implement support for this. But would like to know whether this is something that is somewhere on the radar screen for the future.
--
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 4 months
[Hibernate-JIRA] Commented: (HHH-1233) Allow mixing <union-subclass>and <subclass>
by James Carman (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1233?page=c... ]
James Carman commented on HHH-1233:
-----------------------------------
This issue is ranked 14th (out of 985) out of all of the outstanding issues in JIRA based on votes. So, this isn't some obscure request. I will see what I can do to help implement this.
> Allow mixing <union-subclass>and <subclass>
> -------------------------------------------
>
> Key: HHH-1233
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1233
> Project: Hibernate3
> Issue Type: Improvement
> Components: core
> Environment: N/A
> Reporter: Gunther Schadow
>
> BACKGROUND:
> Hibernate allows mixing <subclass> and <joined-subclass> inheritance mappings but apparently not <subclass> and <union-subclass> mappings, however, this seems like the most useful combination. Example:
> USE CASE:
> We may have a hierarchy with very unevenly distributed mass, i.e., some subclasses have millions of objects, others have only a half-dozen. There may be a lot of different subclasses of the smaller sort.
> Union-subclass seems ideal to work with a dozen different humongous tables, as they can be placed on different tablespaces and managed differently. However, for the 200 or so subclasses whith only a dozen objects each, it would be easier to map these into a single table per sub-hierarchy.
> REQUESTED FEATURE:
> Therefore it seems fair to suggest that <subclass> mappings should be supported underneath <union-subclass> mappings. To allow that the <discriminator> element would have to be handled inside a <union-subclass> element and same for the discriminator-value attribute. Perhaps one could limit the complexity by requiring that the outer mapping must be union-subclass and the inner can be subclass but not vica versa?
> WORKAROUNDS:
> As the documentation mentions one could just create several independent <class> hierarchies, thus effectively emulating the first level of union-subclass specializations. But that would not allow specifying polymorphic associations.
> ESTIMATED EFFORT:
> It could be difficult to implement support for this. But would like to know whether this is something that is somewhere on the radar screen for the future.
--
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 4 months
[Hibernate-JIRA] Commented: (HHH-1233) Allow mixing <union-subclass>and <subclass>
by Steve Ebersole (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1233?page=c... ]
Steve Ebersole commented on HHH-1233:
-------------------------------------
And it makes the most sense to move this discussion over to the dev list. But don't expect us to tell you how to implement the patch. That would require us to investigate it to the degree that we might as well implement it ourselves. We will certainly help you out with specific questions you might run into...
> Allow mixing <union-subclass>and <subclass>
> -------------------------------------------
>
> Key: HHH-1233
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1233
> Project: Hibernate3
> Issue Type: Improvement
> Components: core
> Environment: N/A
> Reporter: Gunther Schadow
>
> BACKGROUND:
> Hibernate allows mixing <subclass> and <joined-subclass> inheritance mappings but apparently not <subclass> and <union-subclass> mappings, however, this seems like the most useful combination. Example:
> USE CASE:
> We may have a hierarchy with very unevenly distributed mass, i.e., some subclasses have millions of objects, others have only a half-dozen. There may be a lot of different subclasses of the smaller sort.
> Union-subclass seems ideal to work with a dozen different humongous tables, as they can be placed on different tablespaces and managed differently. However, for the 200 or so subclasses whith only a dozen objects each, it would be easier to map these into a single table per sub-hierarchy.
> REQUESTED FEATURE:
> Therefore it seems fair to suggest that <subclass> mappings should be supported underneath <union-subclass> mappings. To allow that the <discriminator> element would have to be handled inside a <union-subclass> element and same for the discriminator-value attribute. Perhaps one could limit the complexity by requiring that the outer mapping must be union-subclass and the inner can be subclass but not vica versa?
> WORKAROUNDS:
> As the documentation mentions one could just create several independent <class> hierarchies, thus effectively emulating the first level of union-subclass specializations. But that would not allow specifying polymorphic associations.
> ESTIMATED EFFORT:
> It could be difficult to implement support for this. But would like to know whether this is something that is somewhere on the radar screen for the future.
--
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 4 months
[Hibernate-JIRA] Commented: (HHH-1233) Allow mixing <union-subclass>and <subclass>
by Steve Ebersole (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1233?page=c... ]
Steve Ebersole commented on HHH-1233:
-------------------------------------
Well, you stated that it would be a "VERY nice feature ... please implement it." If it is that important *to you* then implement it. That is the point of open source. Attach your implementation here (the LGPL requires you make the patch available back to the upstream development team) and I'll get it included in a later version and incorporated into the Hibernate codebase. This is the spirit of OSS...
Basically I have enough work on "VERY nice features" which I rate (and other users do as well based on votes) as more pressing. I do not have cycles to implement this myself right now.
And Wouter is completely right. If you are spending many hours working on workarounds, you are probably better served looking at just implementing this feature.
> Allow mixing <union-subclass>and <subclass>
> -------------------------------------------
>
> Key: HHH-1233
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1233
> Project: Hibernate3
> Issue Type: Improvement
> Components: core
> Environment: N/A
> Reporter: Gunther Schadow
>
> BACKGROUND:
> Hibernate allows mixing <subclass> and <joined-subclass> inheritance mappings but apparently not <subclass> and <union-subclass> mappings, however, this seems like the most useful combination. Example:
> USE CASE:
> We may have a hierarchy with very unevenly distributed mass, i.e., some subclasses have millions of objects, others have only a half-dozen. There may be a lot of different subclasses of the smaller sort.
> Union-subclass seems ideal to work with a dozen different humongous tables, as they can be placed on different tablespaces and managed differently. However, for the 200 or so subclasses whith only a dozen objects each, it would be easier to map these into a single table per sub-hierarchy.
> REQUESTED FEATURE:
> Therefore it seems fair to suggest that <subclass> mappings should be supported underneath <union-subclass> mappings. To allow that the <discriminator> element would have to be handled inside a <union-subclass> element and same for the discriminator-value attribute. Perhaps one could limit the complexity by requiring that the outer mapping must be union-subclass and the inner can be subclass but not vica versa?
> WORKAROUNDS:
> As the documentation mentions one could just create several independent <class> hierarchies, thus effectively emulating the first level of union-subclass specializations. But that would not allow specifying polymorphic associations.
> ESTIMATED EFFORT:
> It could be difficult to implement support for this. But would like to know whether this is something that is somewhere on the radar screen for the future.
--
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 4 months
[Hibernate-JIRA] Commented: (HHH-1233) Allow mixing <union-subclass>and <subclass>
by James Carman (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1233?page=c... ]
James Carman commented on HHH-1233:
-----------------------------------
I could spend some cycles on this. It would be useful for one of the gurus to maybe provide a bit of guidance, though. Since I've never worked on the core of hibernate and only used it as a user, it would be great to have some idea of where to start. :)
> Allow mixing <union-subclass>and <subclass>
> -------------------------------------------
>
> Key: HHH-1233
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1233
> Project: Hibernate3
> Issue Type: Improvement
> Components: core
> Environment: N/A
> Reporter: Gunther Schadow
>
> BACKGROUND:
> Hibernate allows mixing <subclass> and <joined-subclass> inheritance mappings but apparently not <subclass> and <union-subclass> mappings, however, this seems like the most useful combination. Example:
> USE CASE:
> We may have a hierarchy with very unevenly distributed mass, i.e., some subclasses have millions of objects, others have only a half-dozen. There may be a lot of different subclasses of the smaller sort.
> Union-subclass seems ideal to work with a dozen different humongous tables, as they can be placed on different tablespaces and managed differently. However, for the 200 or so subclasses whith only a dozen objects each, it would be easier to map these into a single table per sub-hierarchy.
> REQUESTED FEATURE:
> Therefore it seems fair to suggest that <subclass> mappings should be supported underneath <union-subclass> mappings. To allow that the <discriminator> element would have to be handled inside a <union-subclass> element and same for the discriminator-value attribute. Perhaps one could limit the complexity by requiring that the outer mapping must be union-subclass and the inner can be subclass but not vica versa?
> WORKAROUNDS:
> As the documentation mentions one could just create several independent <class> hierarchies, thus effectively emulating the first level of union-subclass specializations. But that would not allow specifying polymorphic associations.
> ESTIMATED EFFORT:
> It could be difficult to implement support for this. But would like to know whether this is something that is somewhere on the radar screen for the future.
--
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 4 months
[Hibernate-JIRA] Commented: (HHH-1233) Allow mixing <union-subclass>and <subclass>
by Wouter Lievens (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1233?page=c... ]
Wouter Lievens commented on HHH-1233:
-------------------------------------
It means - I guess - that if one has the resources to spend dozens of hours on a workaround, it may be a better investment to implement the feature (even if only of experimental internal quality) and donate it to the project.
As much as I really long for this feature, the hibernate team obviously has plenty of work set out. This won't happen anytime soon unless one of us (being; those who need the feature badly) chooses to implement it.
> Allow mixing <union-subclass>and <subclass>
> -------------------------------------------
>
> Key: HHH-1233
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1233
> Project: Hibernate3
> Issue Type: Improvement
> Components: core
> Environment: N/A
> Reporter: Gunther Schadow
>
> BACKGROUND:
> Hibernate allows mixing <subclass> and <joined-subclass> inheritance mappings but apparently not <subclass> and <union-subclass> mappings, however, this seems like the most useful combination. Example:
> USE CASE:
> We may have a hierarchy with very unevenly distributed mass, i.e., some subclasses have millions of objects, others have only a half-dozen. There may be a lot of different subclasses of the smaller sort.
> Union-subclass seems ideal to work with a dozen different humongous tables, as they can be placed on different tablespaces and managed differently. However, for the 200 or so subclasses whith only a dozen objects each, it would be easier to map these into a single table per sub-hierarchy.
> REQUESTED FEATURE:
> Therefore it seems fair to suggest that <subclass> mappings should be supported underneath <union-subclass> mappings. To allow that the <discriminator> element would have to be handled inside a <union-subclass> element and same for the discriminator-value attribute. Perhaps one could limit the complexity by requiring that the outer mapping must be union-subclass and the inner can be subclass but not vica versa?
> WORKAROUNDS:
> As the documentation mentions one could just create several independent <class> hierarchies, thus effectively emulating the first level of union-subclass specializations. But that would not allow specifying polymorphic associations.
> ESTIMATED EFFORT:
> It could be difficult to implement support for this. But would like to know whether this is something that is somewhere on the radar screen for the future.
--
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 4 months
[Hibernate-JIRA] Commented: (HHH-1233) Allow mixing <union-subclass>and <subclass>
by James Carman (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1233?page=c... ]
James Carman commented on HHH-1233:
-----------------------------------
Mr. Bauer,
Does that mean that if an implementation is not attached that you guys won't work on it?
James
> Allow mixing <union-subclass>and <subclass>
> -------------------------------------------
>
> Key: HHH-1233
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1233
> Project: Hibernate3
> Issue Type: Improvement
> Components: core
> Environment: N/A
> Reporter: Gunther Schadow
>
> BACKGROUND:
> Hibernate allows mixing <subclass> and <joined-subclass> inheritance mappings but apparently not <subclass> and <union-subclass> mappings, however, this seems like the most useful combination. Example:
> USE CASE:
> We may have a hierarchy with very unevenly distributed mass, i.e., some subclasses have millions of objects, others have only a half-dozen. There may be a lot of different subclasses of the smaller sort.
> Union-subclass seems ideal to work with a dozen different humongous tables, as they can be placed on different tablespaces and managed differently. However, for the 200 or so subclasses whith only a dozen objects each, it would be easier to map these into a single table per sub-hierarchy.
> REQUESTED FEATURE:
> Therefore it seems fair to suggest that <subclass> mappings should be supported underneath <union-subclass> mappings. To allow that the <discriminator> element would have to be handled inside a <union-subclass> element and same for the discriminator-value attribute. Perhaps one could limit the complexity by requiring that the outer mapping must be union-subclass and the inner can be subclass but not vica versa?
> WORKAROUNDS:
> As the documentation mentions one could just create several independent <class> hierarchies, thus effectively emulating the first level of union-subclass specializations. But that would not allow specifying polymorphic associations.
> ESTIMATED EFFORT:
> It could be difficult to implement support for this. But would like to know whether this is something that is somewhere on the radar screen for the future.
--
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 4 months
[Hibernate-JIRA] Commented: (HHH-1233) Allow mixing <union-subclass>and <subclass>
by Christian Bauer (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1233?page=c... ]
Christian Bauer commented on HHH-1233:
--------------------------------------
Attach your implementation.
> Allow mixing <union-subclass>and <subclass>
> -------------------------------------------
>
> Key: HHH-1233
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1233
> Project: Hibernate3
> Issue Type: Improvement
> Components: core
> Environment: N/A
> Reporter: Gunther Schadow
>
> BACKGROUND:
> Hibernate allows mixing <subclass> and <joined-subclass> inheritance mappings but apparently not <subclass> and <union-subclass> mappings, however, this seems like the most useful combination. Example:
> USE CASE:
> We may have a hierarchy with very unevenly distributed mass, i.e., some subclasses have millions of objects, others have only a half-dozen. There may be a lot of different subclasses of the smaller sort.
> Union-subclass seems ideal to work with a dozen different humongous tables, as they can be placed on different tablespaces and managed differently. However, for the 200 or so subclasses whith only a dozen objects each, it would be easier to map these into a single table per sub-hierarchy.
> REQUESTED FEATURE:
> Therefore it seems fair to suggest that <subclass> mappings should be supported underneath <union-subclass> mappings. To allow that the <discriminator> element would have to be handled inside a <union-subclass> element and same for the discriminator-value attribute. Perhaps one could limit the complexity by requiring that the outer mapping must be union-subclass and the inner can be subclass but not vica versa?
> WORKAROUNDS:
> As the documentation mentions one could just create several independent <class> hierarchies, thus effectively emulating the first level of union-subclass specializations. But that would not allow specifying polymorphic associations.
> ESTIMATED EFFORT:
> It could be difficult to implement support for this. But would like to know whether this is something that is somewhere on the radar screen for the future.
--
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 4 months
[Hibernate-JIRA] Commented: (HHH-1233) Allow mixing <union-subclass>and <subclass>
by Joe Feeley (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1233?page=c... ]
Joe Feeley commented on HHH-1233:
---------------------------------
Adding this feature would save us dozens of hours of data migration that simply adds complexity to our schema, etc.
> Allow mixing <union-subclass>and <subclass>
> -------------------------------------------
>
> Key: HHH-1233
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1233
> Project: Hibernate3
> Issue Type: Improvement
> Components: core
> Environment: N/A
> Reporter: Gunther Schadow
>
> BACKGROUND:
> Hibernate allows mixing <subclass> and <joined-subclass> inheritance mappings but apparently not <subclass> and <union-subclass> mappings, however, this seems like the most useful combination. Example:
> USE CASE:
> We may have a hierarchy with very unevenly distributed mass, i.e., some subclasses have millions of objects, others have only a half-dozen. There may be a lot of different subclasses of the smaller sort.
> Union-subclass seems ideal to work with a dozen different humongous tables, as they can be placed on different tablespaces and managed differently. However, for the 200 or so subclasses whith only a dozen objects each, it would be easier to map these into a single table per sub-hierarchy.
> REQUESTED FEATURE:
> Therefore it seems fair to suggest that <subclass> mappings should be supported underneath <union-subclass> mappings. To allow that the <discriminator> element would have to be handled inside a <union-subclass> element and same for the discriminator-value attribute. Perhaps one could limit the complexity by requiring that the outer mapping must be union-subclass and the inner can be subclass but not vica versa?
> WORKAROUNDS:
> As the documentation mentions one could just create several independent <class> hierarchies, thus effectively emulating the first level of union-subclass specializations. But that would not allow specifying polymorphic associations.
> ESTIMATED EFFORT:
> It could be difficult to implement support for this. But would like to know whether this is something that is somewhere on the radar screen for the future.
--
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 4 months