You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by Craig Russell <Cr...@Sun.COM> on 2005/05/28 00:24:59 UTC
Problem in tck20 with Company model
Hi,
We are getting this error with the checked-in code running a new test.
Could you please take a look?
tck - Exception during setUp or runtest:
<javax.jdo.JDODataStoreException: Add request failed : INSERT INTO
EMPLOYEE_PROJECTS (PERSONID_OID,PROJID_EID) VALUES (?,?)
[java] NestedThrowables:
[java] SQL Exception: Table 'EMPLOYEE_PROJECTS' does not
exist.>javax.jdo.JDODataStoreException: Add request failed : INSERT
INTO EMPLOYEE_PROJECTS (PERSONID_OID,PROJID_EID) VALUES (?,?)
We are running datastore identity with the new test case
maven -o -Dtest=mapping.CompletenessTest runtck.jdorisingle
There is no table EMPLOYEE_PROJECTS in the .orm file, so JPOX must be
imagining it (generating the table name from the class names).
Thanks,
Craig
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Problem in tck20 with Company model
Posted by Craig Russell <Cr...@Sun.COM>.
Hi Andy,
On May 27, 2005, at 11:54 PM, Andy Jefferson wrote:
>> We are getting this error with the checked-in code running a new test.
>> Could you please take a look?
>> There is no table EMPLOYEE_PROJECTS in the .orm file, so JPOX must be
>> imagining it (generating the table name from the class names).
>
> Hi Craig,
>
> it results from you wanting to specify the minimum info necessary in
> your
> MetaData :-).
This really is an ease of use objective. If you have to specify the
same information twice, you are twice as likely to make a mistake.
> In this case the name for the join table is specified on just
> one side (and JPOX currently has a default of having a separate join
> table
> for each side of the relation - like 2 independent 1-N's). Will be
> fixed in
> the next nightly build (20050529).
Great, thanks!
Craig
>
> --
> Andy
> JPOX - Java Persistent Objects
>
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Problem in tck20 with Company model
Posted by Andy Jefferson <an...@jpox.org>.
> We are getting this error with the checked-in code running a new test.
> Could you please take a look?
> There is no table EMPLOYEE_PROJECTS in the .orm file, so JPOX must be
> imagining it (generating the table name from the class names).
Hi Craig,
it results from you wanting to specify the minimum info necessary in your
MetaData :-). In this case the name for the join table is specified on just
one side (and JPOX currently has a default of having a separate join table
for each side of the relation - like 2 independent 1-N's). Will be fixed in
the next nightly build (20050529).
--
Andy
JPOX - Java Persistent Objects