Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda: 1. Query timeout in JDO / Update timeouta. Should we have different settings for query/read versus insert/ update/delete? Jorg says that *update* operations might need their own setting.
b. Should the timeout apply to *any* in-vm operations, or just to datastore operations? The original rationale for timeout was specifically to allow setting the underlying datastore timeout value.
c Should we rename the property/api something like DatastoreRead and DatastoreWrite? This might make it more clear that queries, getObjectById, refresh, and others are affected.
AI Craig update the JIRA with new proposal 2. Query objects and hashCode() + equals()This issue looks like it has been resolved. If further action is necessary, please file a JIRA.
3. Dependence of RI on JPA2Looks like this issue is moot. Based on our changes to JDO 2.3 and the fact that JPA2 is now in JCP vote, there are no timing issues.
4. Other issuesIf-then-else support for JDOQL: It looks like JPA2 will support this; SQL supports it; are there any issues with non-SQL datastores?
Action Items from weeks past:AI Nov 13 08 Michael: Take a look at what changes would be needed in the BNF to support for if-then-else in JDOQL, reply to the original email, open a JIRA
Craig L Russell Architect, Sun Java Enterprise System http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@sun.com P.S. A good JDO? O, Gasp!
smime.p7s
Description: S/MIME cryptographic signature
