Menu
▾
▴
nhibernate-issues
|
[nhibernate-issues] [JIRA] Created: (NH-1681) Update Join element
to support keys with property-refs
From: NHibernate J. <nh...@gm...> - 2009-02-13 16:57:06
|
Update Join element to support keys with property-refs
------------------------------------------------------
Key: NH-1681
URL: http://jira.nhibernate.org/browse/NH-1681
Project: NHibernate
Issue Type: Improvement
Components: Core
Affects Versions: 2.1.0.Alpha1
Reporter: Daniel Guenter
Priority: Minor
Attachments: 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://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Daniel G. (JIRA) <nh...@gm...> - 2011-03-02 15:53:26
|
[ http://216.121.112.228/browse/NH-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Guenter updated NH-1681:
-------------------------------
Attachment: NH3.0.0.GA ref join.patch
I've updated my fully functioning patch to work against the 3.0 GA repository.
All tests pass.
It would be nice if it could be rolled into the trunk.
> 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
|
|
From: David A. (JIRA) <nh...@gm...> - 2011-05-10 17:44:01
|
[ http://216.121.112.228/browse/NH-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21037#action_21037 ]
David Alpert commented on NH-1681:
----------------------------------
This issue just bit our project. We have exactly this scenario and can work around it by writing a View. It would be super nice to roll this functionality into the trunk!
> 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
|
|
From: Aren B. (JIRA) <nh...@gm...> - 2011-05-10 22:22:04
|
[ http://216.121.112.228/browse/NH-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21044#action_21044 ]
Aren Blondahl commented on NH-1681:
-----------------------------------
I agree, this looks like a feature I'd like to see in trunk very much.
> 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
|
|
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
|
|
From: Daniel G. (JIRA) <nh...@gm...> - 2011-06-15 18:24:34
|
[ http://216.121.112.228/browse/NH-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21297#action_21297 ]
Daniel Guenter commented on NH-1681:
------------------------------------
Yes it is the same.
> 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
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X