From: David M. (JIRA) <nh...@gm...> - 2011-06-15 18:20:33
|
[ http://216.121.112.228/browse/NH-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21295#action_21295 ] David McClelland commented on NH-1681: -------------------------------------- Is this the same as NH-1452? > Update Join element to support keys with property-refs > ------------------------------------------------------ > > Key: NH-1681 > URL: http://216.121.112.228/browse/NH-1681 > Project: NHibernate > Issue Type: Improvement > Components: Core > Affects Versions: 2.1.0.Alpha1 > Reporter: Daniel Guenter > Priority: Minor > Attachments: NH3.0.0.GA ref join.patch, NHibernateJoinPatch.patch > > > <join> element has typically only supported joining to PK of owning table. Sometimes this is limiting especially in dealing with legacy databases where multiple unique keys may be present. It would be nice to be able to specify a property-ref in the <key> element. > Patch included updates functionality to add the aforementioned improvement. The only caveat is that the column mapped as the property-ref must be marked as unique as well. This patch is kind of invasive as it has to change major functionality to allow specifying of alternate ID's on save/update/delete and in the join query. This patch also supports proper exporting of the schema. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://216.121.112.228/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |