Duplicate
Details
Details
Assignee
Unassigned
UnassignedReporter
Daniel Guenter
Daniel GuenterComponents
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
<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.