Attendees: Michelle Caisse, Michael Bouschen, Matthew Adams, Craig Russell

Agenda:

1. TCK State Transitions test. Awaiting a JIRA/patch from Andy?

2. JDOQL : Bulk Update and Delete Operations  
https://issues.apache.org/jira/browse/JDO-617

This update is to show how the proposed type safe query would implement the requested bulk update and delete.

JDO does not, by design, support updates via query. The issues are around how to support the callbacks and synchronize the cache with the data updated in the datastore. AI Matthew comment on the JIRA.

Another issue is whether the update operator is really useful. AI Craig comment on the JIRA.

3. Maven 2 upgrade https://issues.apache.org/jira/browse/JDO-647

After upgrading the system, Michelle is running into issues running under Netbeans with Maven 3. Still troubleshooting.

4. Other issues

Action Items from weeks past:
[Feb 25 2011] AI Michael, Craig, other volunteers: Look at Typesafe ... query capability for JDOQL https://issues.apache.org/jira/browse/JDO-652

Michael has started to set up an environment in which to test the typesafe query. There are new dependencies if we want to run the tck (which also has schema and queries already set up).

Need to run the tck with dependencies on DataNucleus until a patch for JDO name space is applied.

There are some high level questions how to integrate query into the existing query interfaces.

The query definition is acquired from a PersistenceManager, which may make it awkward to share among multiple PersistenceManagers. All you really need is PersistenceMangerFactory until you want to execute it.

The typesafe query is bound to both the PersistenceManager and the parameter values. JDO query does not bind parameters, but the API allows binding to occur on the execute statement itself.


Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:craig.russ...@oracle.com
P.S. A good JDO? O, Gasp!

Reply via email to