db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Jefferson (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (JDO-211) SQL Exception: 'ADPT_PK_IDX' is not a column in table or VTI 'APPLICATIONIDENTITY0.HASHMAP_OBJECT0_STR'.
Date Mon, 14 Nov 2005 18:03:29 GMT
     [ http://issues.apache.org/jira/browse/JDO-211?page=all ]

Andy Jefferson reassigned JDO-211:

    Assign To: Michelle Caisse  (was: Andy Jefferson)

Agree with Craig wrt app identity. JPOX should (and indeed does in JPOX CVS - builds 15/11/2005
onwards) use the app id fields of the key as part of the PK when the user hasn't specified
the PK, so no need to add the PK spec for that identity case.

It shows up some schema mapping issues. For example in HashMapStringValueCollections (app
identity) there is a field HashMapOfSimpleClass_String12 that has an embedded key (SimpleClass),
which has no <embedded> definition, and which has a schema consisting of a single column
for that embedded key.

It also gets through to the actual test of expected versus actual on MapStringValueCollections
(app identity) with the failure being in the comparison process - the values are correct by
my reckoning

> 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: Michelle Caisse

> 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:
For more information on JIRA, see:

View raw message