[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2060?page=c... ] Jacob Robertson commented on HHH-2060: -------------------------------------- My company has a very similar need. In our case, the Data teams have determined that for particular high-volume tables, we will assign a surrogate "GUID" that is spread across two DEC(11) columns. This decision is completely out of the hands of the java developers. We are looking into using things like Interceptor (as Gavin seems to recommend in HD-389) to handle this, but it would certainly be a much simpler solution to do what Xavier shows. I notice that this issue has remained un-commented on for almost a year now, and the previous issue (under Hibernate-2) was marked as "rejected" with Gavin's comment that "a synthetic composite key is non-meaningful". Is there any chance of re-visiting this? If not, perhaps this issue could also be closed and "rejected" with some further explanation. Otherwise, we have demonstrated a real-world need for this feature, and Xavier seems to have demonstrated that is would be simple for Hibernate to make this feature available. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2060?page=c... ] Christian Bauer commented on HHH-2060: -------------------------------------- What is needed now is obviously for someone to demonstrate that they can code and attach a patch. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2060?page=c... ] Jacob Robertson commented on HHH-2060: -------------------------------------- @Steve - what is the threshold for getting an issue "rejected" - the previous issue had 0 votes and got Gavin's attention. ;) @Christian - I believe the whole point of Xavier's original comment was that there is no code change necessary. "The current code of Hibernate manages it very well" was the way he phrased it. I'll look into confirming this one way or the other - I may have interpretted Xavier's comment too judiciously. P.S. Thanks for your timely (though snarky) responses! -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2060?page=c... ] Jacob Robertson commented on HHH-2060: -------------------------------------- @Steve I submitted my last comment while you were posting the previous comment, and hadn't read it yet, so my comment was 2 minutes out of date. I understand where you're coming from - the DTD won't be changed until a true test is written. I get that. And I noticed the History Change to that effect as well. No need to pound that point in further. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2060?page=c... ] Paul Benedict commented on HHH-2060: ------------------------------------ I totally concur that allowing generators for a composite key is an important feature. This issue now has 7 votes. Let's get this into Hibernate 3.3 -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2060?page=c... ] Jonathan S Fisher commented on HHH-2060: ---------------------------------------- Hello hibernate friends :) I think since this does not involve a major code change, but merely a DTD change, this should be considered for incorporation into 3.3. My company has spent time developing a test case to prove Hibernate will support this change. If the tests could be reviewed I think this is a minor change that would benefit many people: Many developers are "locked into" or handed a schema that was not designed specifically for hibernate. Thank you for your consideration. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2060?page=c... ] Steve Ebersole updated HHH-2060: -------------------------------- Requires Release Note: [Affirmative] -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2060?page=c... ] Paul Benedict commented on HHH-2060: ------------------------------------ Steve, because the DTD has changed, would it make more sense to create a 3.3 DTD? It's really not a 3.0 DTD anymore. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2060?page=c... ] Sandeep Vaid commented on HHH-2060: ----------------------------------- My scenario is also similar... http://forum.hibernate.org/viewtopic.php?t=995903&sid=1e523284ccc4b1c... When i try to save Product (with cascade save for ProductBasic), i get the following error: org.hibernate.PropertyAccessException: IllegalArgumentException occurred calling getter of com.tietoenator.lis.db.impl.product.bo.CompProductBasicBO.useType at org.hibernate.property.BasicPropertyAccessor$BasicGetter.get(BasicPropertyAccessor.java:171) at org.hibernate.tuple.component.AbstractComponentTuplizer.getPropertyValue(AbstractComponentTuplizer.java:64) at org.hibernate.tuple.component.AbstractComponentTuplizer.getPropertyValues(AbstractComponentTuplizer.java:70) at org.hibernate.tuple.component.PojoComponentTuplizer.getPropertyValues(PojoComponentTuplizer.java:86) at org.hibernate.type.ComponentType.getPropertyValues(ComponentType.java:353) at org.hibernate.type.ComponentType.getHashCode(ComponentType.java:184) at org.hibernate.engine.EntityKey.generateHashCode(EntityKey.java:104) at org.hibernate.engine.EntityKey.<init>(EntityKey.java:48) at org.hibernate.event.def.AbstractSaveEventListener.performSave(AbstractSaveEventListener.java:161) I guess as i have used composite id and <generator class="foreign"> inside that, it treats it as component and when it tries to get a unique key for the instance using hashmap(), it throws exception.. I guess this is a bug in hibernate core... I have checked this with Hibernate 3.2.6 and Hibernate 3.3.1 as well -- 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