Update Join element to support keys with property-refs

Description

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

Environment

None

Attachments

2

Activity

Show:

Daniel Guenter April 24, 2012 at 9:54 PM

Moshe F. November 14, 2011 at 11:58 AM

This patch fixed a major problem.
Is it possible to fix 2 more problem?
The ability to make multiple join to another table by different foreign keys.
The ability to make a nested join, using a property from a foreign key join to make another foreign key join to a third table,

Daniel Guenter June 15, 2011 at 11:23 AM

Yes it is the same.

David McClelland June 15, 2011 at 11:19 AM

Is this the same as NH-1452?

Aren Blondahl May 10, 2011 at 3:21 PM

I agree, this looks like a feature I'd like to see in trunk very much.

Duplicate

Assignee

Reporter

Components

Affects versions

Priority

Who's Looking?

Open Who's Looking?
Created February 13, 2009 at 8:54 AM
Updated January 10, 2013 at 12:28 PM
Resolved January 10, 2013 at 12:28 PM
Who's Looking?