Issue Details (XML | Word | Printable)

Key: JDO-215
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Michelle Caisse
Reporter: Craig Russell
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
JDO

Remove <order> from mapping for HashSetCollections and SetCollections.

Created: 17/Nov/05 06:29 AM   Updated: 02/Dec/05 09:24 AM
Return to search
Component/s: tck2
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

File Attachments:
  Size
Text File Licensed for inclusion in ASF works JDO-215.patch 2005-11-18 08:21 AM Michelle Caisse 61 kB

Resolution Date: 02/Dec/05 09:24 AM


 Description  « Hide
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.


 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Michelle Caisse made changes - 18/Nov/05 06:55 AM
Field Original Value New Value
Assignee Michelle Caisse [ mcaisse ]
Michelle Caisse made changes - 18/Nov/05 07:44 AM
Status Open [ 1 ] In Progress [ 3 ]
Michelle Caisse made changes - 18/Nov/05 08:21 AM
Attachment JDO-215.patch [ 12320767 ]
Michelle Caisse made changes - 19/Nov/05 02:14 AM
Status In Progress [ 3 ] Open [ 1 ]
Craig Russell made changes - 19/Nov/05 02:14 AM
Assignee Michelle Caisse [ mcaisse ] Andy Jefferson [ andy ]
Craig Russell made changes - 22/Nov/05 04:51 AM
Assignee Andy Jefferson [ andy ] Michelle Caisse [ mcaisse ]
Michelle Caisse made changes - 02/Dec/05 09:24 AM
Status Open [ 1 ] Resolved [ 5 ]
Resolution Fixed [ 1 ]