db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michelle Caisse (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JDO-215) Remove <order> from mapping for HashSetCollections and SetCollections.
Date Fri, 02 Dec 2005 00:26:31 GMT
     [ http://issues.apache.org/jira/browse/JDO-215?page=all ]
     
Michelle Caisse resolved JDO-215:
---------------------------------

    Resolution: Fixed

I believe this is now a dup of JDO-211, thus resolved by revision 351537.

> 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 <order>
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, since 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/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message