JDO TCK Conference Call Friday June 3, 9:30 AM Pacific Daylight Time (PDT)

[Michael Bouschen <mi...@akquinet.de>]

Hi,

We will have our regular meeting Friday, June 3 at 9:30 AM Pacific Daylight Time (PDT) to discuss JDO TCK issues and status. 

We use the new dial-in for audio and video. You need a Skype account to join.
https://join.skype.com/RUHyGMHxNDyR 

Agenda:
1. EMail "A new general method to update object databases / Should it be included in Java Data Objects, JDO ?"
2. Discussion "EmbeddedPCMapping cannot be cast to PersistableMapping"
3. New patch JDO-751 "Support for Java8 Optional" https://issues.apache.org/jira/browse/JDO-751
4. JDO-747 Behavior of delete() with multiple concurrent Transactions" https://issues.apache.org/jira/browse/JDO-747
5. JDO 3.1: Need to go through change lists in JIRA for 3.1 RC1 and 3.1 to prepare JCP Change Log
6. Other issues

Action Items from weeks past:
[Oct 30 2015] AI Craig: File a maintenance review with JCP
[May 15 2015] AI Craig Spec change for roll back an active transaction when closing a persistence manager (JDO-735)  
[Apr 17 2015] AI Craig: Oracle spec page on JDO need to be updated once the JCP Maintenance Release for JDO 3.1 is published
[Oct 17 2014] AI Matthew any updates for "Modify specification to address NoSQL datastores": https://issues.apache.org/jira/browse/JDO-651?
[Feb 28 2014] AI Everyone: take a look at https://issues.apache.org/jira/browse/JDO-712
[Feb 28 2014] AI Everyone: take a look at https://issues.apache.org/jira/browse/JDO-625
[Dec 13 2013] AI Craig file a JIRA for java.sql.Blob and java.sql.Clob as persistent field types
[Aug 24 2012] AI Craig update the JIRAs JDO-689 JDO-690 and JDO-692 about JDOHelper methods. In process.

Regards Michael


-- 
Michael Bouschen
akquinet tech@spree GmbH
B�lowstra�e 66 \u2022 D-10783 Berlin
Tel:   +49 30 235520-33
Fax:  +49 30 217520-12

E-Mail: michael.bouschen@akquinet.de <ma...@akquinet.de>
Web:   www.akquinet.de <http://www.akquinet.de/>

Gesch�ftsf�hrung: Martin Weber, Dr. Torsten Fink
Amtsgericht Berlin HRB 86780 \u2022 USt.-Id. Nr.: DE 225 964 680

[Facebook] <http://www.facebook.com/akquinet>  [XING]
<https://www.xing.com/companies/akquinetag>  [G+]
<https://plus.google.com/b/111054946250796705170/+akquinet/posts> 
[LinkedIn] <https://www.linkedin.com/company/akquinet-ag>  [Twitter]
<https://twitter.com/akquinet>

Minutes: JDO TCK Conference Call Friday June 3, 9:30 AM Pacific Daylight Time (PDT)

[Craig Russell <cr...@oracle.com>]

Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell

Agenda:

1. EMail "A new general method to update object databases / Should it be included in Java Data Objects, JDO ?”

There has been no more discussion; it’s not clear that the author understands JDO, especially how JDO manages objects in memory organized in a graph.

2. Discussion "EmbeddedPCMapping cannot be cast to PersistableMapping”

Probably not related to optional. Seems to be a bug in datanucleus. AI Michael update query test case to specifically test for “double NOT” and file a bug. 
Possible test scenarios:
!(field != value)
!(field != null)
!!(field != value)
!!(field != null)
!!!(field != value)
!!!(field != null)

3. New patch JDO-751 "Support for Java8 Optional" https://issues.apache.org/jira/browse/JDO-751

Reviewed Tilmann’s message from June 1:

query #2=  "optionalPC.get().id == " + DUMMY_ID
returns the dummy object instead of the object that references the dummy object; probably a bug in datanucleus

query: "optionalPC == null”
returns objects in the datastore that either have optionalPC empty or null; datanucleus stores empty objects as null in the datastore; ok behavior

query "!(optionalPC == null)”
returns objects in the datastore that have optionalPC not null but not objects where optionalPC empty; ok behavior because datanucleus stores empty objects as null

do we really need to have jdoql implement optional.orElse? the test case for orElse doesn’t make a strong case for it.
The use of orElse in Java is not in question, but we should try to find a good use-case for it in jdoql. 

Need proposed specification changes. AI Craig

4. JDO-747 Behavior of delete() with multiple concurrent Transactions" https://issues.apache.org/jira/browse/JDO-747

5. JDO 3.1: Need to go through change lists in JIRA for 3.1 RC1 and 3.1 to prepare JCP Change Log

6. Other issues

Action Items from weeks past:
[Oct 30 2015] AI Craig: File a maintenance review with JCP
[May 15 2015] AI Craig Spec change for roll back an active transaction when closing a persistence manager (JDO-735)  
[Apr 17 2015] AI Craig: Oracle spec page on JDO need to be updated once the JCP Maintenance Release for JDO 3.1 is published
[Oct 17 2014] AI Matthew any updates for "Modify specification to address NoSQL datastores": https://issues.apache.org/jira/browse/JDO-651?
[Feb 28 2014] AI Everyone: take a look at https://issues.apache.org/jira/browse/JDO-712
[Feb 28 2014] AI Everyone: take a look at https://issues.apache.org/jira/browse/JDO-625
[Dec 13 2013] AI Craig file a JIRA for java.sql.Blob and java.sql.Clob as persistent field types
[Aug 24 2012] AI Craig update the JIRAs JDO-689 JDO-690 and JDO-692 about JDOHelper methods. In process.

Craig L Russell
Architect
craig.russell@oracle.com
P.S. A good JDO? O, Gasp!