Hi Andy,

On Aug 20, 2005, at 2:25 AM, Andy Jefferson wrote:

CollectionOfObject doesn't work JDO-121. AI: Need feedback from Erik
or Andy.


Feedback : CollectionCollections has a field Object1 that is a 
Collection<SimpleClass> embedded in the join table. The TCK is expecting a 
schema with join table having columns for the FK back to the owner object, 
and the fields for the element. JPOX looks at this from a different angle and 
requires a PK on this join table and so, since we don't have an id for the 
embedded SimpleClass, we add an "adapter index" column to form the PK. As has 
been discussed in the past, the user has no obvious way of saying that they 
don't want a PK applying to the join table. They have the <primary-key> 
element but that is only currently for specifying the pk name.

There is a natural PK for the join table. It's a combination of the FK plus the column mapped to the id field. If this were defined to be the PK for the join table in the schema, would that work?

Craig


In addition, since the test is using java.util.Collection, which can allow 
duplicates, the JDO impl can utilise an "adapter index" in the same way to 
allow duplicates in the join table.



-- 
Andy
Java Persistent Objects - JPOX


Craig Russell

Architect, Sun Java Enterprise System http://java.sun.com/products/jdo

408 276-5638 mailto:[EMAIL PROTECTED]

P.S. A good JDO? O, Gasp!


Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to