|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
02/Dec/05 09:24 AM
|
|
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.
|
|
Description
|
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.
|
Show » |
| No work has yet been logged on this issue.
|
|
Bug
Resolved
Major
Remove <order> from mapping for HashSetCollections and SetCollections.
