[
http://issues.apache.org/jira/browse/JDO-211?page=comments#action_12358175 ]
Andy Jefferson commented on JDO-211:
------------------------------------
I see that the MetaData is now, for example
<field name="HashMapOfObject_String3" table="HASHMAP_OBJECT3_STR">
<join column="IDENTIFIER"/>
<key>
<embedded>
<field name="id" primary-key="true" column="ID"/>
<field name="intField" column="INTVAL"/>
<field name="stringField" column="STRINGVAL"/>
</embedded>
</key>
<value column="VALUEVAL"/>
</field>
That certainly doesnt agree with my definition of a PK specification for the
join table. It should be (IMHO) like this
<join>
<primary-key>
<column name="IDENTIFIER"/>
<column name="ID"/>
</primary-key>
</join>
which nicely defines the colums to be used for the join table. Using fields of
an embedded object and specifying primary-key there is not logical to me, and
not supported by JPOX either. The JPOX online docs
http://www.jpox.org/docs/1_1/constraints.html
provides what we support for PK definition, which is that above.
> SQL Exception: 'ADPT_PK_IDX' is not a column in table or VTI
> 'APPLICATIONIDENTITY0.HASHMAP_OBJECT0_STR'.
> --------------------------------------------------------------------------------------------------------
>
> Key: JDO-211
> URL: http://issues.apache.org/jira/browse/JDO-211
> Project: JDO
> Type: Bug
> Components: tck20
> Reporter: Michelle Caisse
> Assignee: Andy Jefferson
> Attachments: JDO-211.patch
>
> Test*MapStringValueCollections there is a mismatch between orm and schema.
--
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
