Re: Minutes: JDO TCK Conference Call Friday January 29, 9 AM Pacific Time (PST)
> 2. Spec updates JDO-749 "Support for java.time types, and querying using > associated methods" https://issues.apache.org/jira/browse/JDO-749 > > Chapter 14: why are other supported time types not orderable? No reason, I simply added LocalDateTime, LocalDate, LocalTime where Date was previously mentioned - this could become supported java.time types. But then there are other types not mentioned in that section that are supported as persistable (Locale, Calendar, etc), so why were they excluded?. Same applies in Result Class Requirements section. > Chapter 18: why don't other supported time types not have default JDBC types? Because the default still needs defining. To give an example java.time.YearMonth can be persisted (by DN) as * String * DATE (setting day to 0) * (INT, INT) storing the year and month. > There is special treatment for Local time, date, and date time. Are there > implementation issues? I see no implementation issue, and I also see no "special treatment" (in the spec). Where? > 4. Other issues > > There are several un-accepted changes in the specification noticed during > review of changes in JIRA issues. Do you mean "Track Changes" is ON in the spec docs in SVN? clearly, because the tracked changes in those docs are what has changed since 3.1 (so that it is easier to compile a list of changes when 3.2/4.0 is ever released). Or maybe you mean something else When is there confirmation of what this release is to be called? I'm assuming 3.2, but such a thing should be decided up front when the scope of changes is visible ... which it is. Regards -- Andy DataNucleus (Web: http://www.datanucleus.org Twitter: @datanucleus)
Minutes: JDO TCK Conference Call Friday January 29, 9 AM Pacific Time (PST)
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell Agenda: 1. JDO 3.1: Need to go through change lists in JIRA for 3.1 RC1 and 3.1 to prepare JCP Change Log no change 2. Spec updates JDO-749 "Support for java.time types, and querying using associated methods" https://issues.apache.org/jira/browse/JDO-749 Chapter 14: why are other supported time types not orderable? Chapter 18: why don't other supported time types not have default JDBC types? Appendix D: changes look good There is special treatment for Local time, date, and date time. Are there implementation issues? 3. JIRA JDO-747 "Behavior of delete() with multiple concurrent Transactions" https://issues.apache.org/jira/browse/JDO-747 Still waiting for feedback on the specification updates. Are there any implementation issues? 4. Other issues There are several un-accepted changes in the specification noticed during review of changes in JIRA issues. Are there any current toll-free numbers for Germany and Switzerland? The link to viewvc in page http://db.apache.org/jdo/svn.html uses https:// Can this use http:// instead? AI Tilmann file a JIRA. 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.
