Agenda:
1. Query test failure: Michael ran the test against Oracle. Some difficult issues with schema naming and teardown. It looks like Oracle returns the expected number of rows.
Issues found while working this problem:a. Oracle treats "application0.PERSONS" different from Derby. Oracle expects a user called application0; Derby expects a schema called application0. AI Michael file a JIRA for discussion
b. A minor bug in QueryTest in using variable pm from the superclass; the variable might not have been initialized.
c. Sometimes the test testMultipleProjectionWithConstraints succeeds; sometimes it fails. Might be related to query optimization by Derby. AI Craig update DERBY JIRA.
d. Logging has changed from JPOX 1.1 to 1.2. The logging categories need to be updated in the tck2 src/conf/log4j.properties. AI Michael update the properties in tck2 and tck2-legacy.
e. There seems to be a typo in Andy's comments posting the SQL. Some lines in the innermost WHERE clause are duplicated.
f. Using Oracle, the correct number of rows is returned for all the queries.
2. Updated spec: in progress. The jdoconfig.xml has been added to Appendix D. Should we also put jdo.xml, orm.xml, and jdoquery.xml to Appendix D? No, probably better to add the dtd version of jdoconfig to Appendix D.
AI Michelle look at how to automatically include the xsd and dtd files into the spec.
3. Other issuesSubquery testing: Michael has finished the test creation, and will check in the tests to the tck. AI Michael file a new JIRA if JPOX fails the tests.
While working the subquery test issue, we notice that none of the tests supports memory queries using candidate collection. AI Craig file a JIRA for future release to better test memory queries. Should a couple of query tests be added, or try to run all of the existing query tests against memory?
Action Items from weeks past:[Nov 30 2007] AI Christiaan propose more details on Update/copy by query for post-JDO 2.1.
[May 25 2007] AI everyone download the Grails demo from grails.org and check it out. Also look at Grails/Groovy ExpandoMetaClass that has the magic to avoid reflection and enhancement.
[May 25 2007] AI Matthew Adams prepare a proposal with just the basics of schema synchronization with jdo and orm metadata.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide directing attention to the site. T-shirts. AI: Craig write a ServerSide article.
-- Michelle 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!
smime.p7s
Description: S/MIME cryptographic signature
