| Michael Watzek (JIRA) 2006-03-30, 11:57 pm |
| [ http://issues.apache.org/jira/brows...action_12372236 ]
Michael Watzek commented on JDO-354:
------------------------------------
I noticed that there is a little mismatch between test case MakePersistent, the .sql files, and the .orm files for mappings 5, 6, 7 wrt. which persistence capable classes are needed:
- Test case MakePersistent uses pc class PCPoint only.
- The .sql files create tables PCPoint and PCRect.
- The .orm files specifiy metadata for pc classes PCPoint, PCPoint2, PCRect, and PrimitiveTypes.
This holds true for application identity and datastore identity as well. Does it make sense to erase PCRect in the .sql files and to erase PCPoint2, PCRect, and PrimitiveTypes in the .orm files?
[vbcol=seagreen]
> org.apache.jdo.tck.api.persistencemanager.lifecycle.MakePersistent may fail on teardown
> ---------------------------------------------------------------------------------------
>
> Key: JDO-354
> URL: http://issues.apache.org/jira/browse/JDO-354
> Project: JDO
> Type: Bug
> Components: tck20
> Versions: JDO 2 beta
> Reporter: Michelle Caisse
> Assignee: Michelle Caisse
> Fix For: JDO 2 final
> Attachments: JDO-354.patch
>
> When invoked from a configuration that does not use the default schema, MakePersistent fails because it queries for classes to tear down that do not exist in the current schema.
> testMakePersistent
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secur...nistrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|