[ http://issues.apache.org/jira/browse/JDO-215?page=all ]

Craig Russell reassigned JDO-215:
---------------------------------

Assign To: Michelle Caisse  (was: Andy Jefferson)

This is the same issue as JDO-211. So I agree that the metadata should look 
like:

<field name="HashSetOfObject1" table="HASHSET_OF_OBJECT1">
<join column="IDENTIFIER">
<primary-key>
<column name="IDENTIFIER"/>
<column name="ID"/>
</primary-key>
</join>
<element>
<embedded>
<field name="id" column="ID"/>
<field name="intField" column="INTVAL"/>
<field name="stringField" column="STRINGVAL"/>
</embedded>
</element>
</field>


> Remove <order> from mapping for HashSetCollections and SetCollections.
> ----------------------------------------------------------------------
>
>          Key: JDO-215
>          URL: http://issues.apache.org/jira/browse/JDO-215
>      Project: JDO
>         Type: Bug
>   Components: tck20
>     Reporter: Craig Russell
>     Assignee: Michelle Caisse
>  Attachments: JDO-215.patch
>
> The mapping for HashSetCollections and SetCollections incorrectly have <or
der> columns.
> There should not be an ordering specified for the join table since duplicates are 
not allowed. The mapping for application identity should not need a primary key, sin
ce the JDO implementation should be able to figure out that the primary key is part 
of
the Map.key, but the datastore identity mapping does need a primary key (and
 again, I'd use the id field of SimpleClass as the join table key column.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secur...nistrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira

[ Post a follow-up to this message ]