You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by Michael Bouschen <mi...@akquinet.de> on 2016/10/27 19:12:47 UTC
JDO TCK Conference Call Friday October 28, 9 AM Pacific Daylight Time
(PDT)
Hi,
We will have our regular meeting Friday, October 28 at 9 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/euV54RJwJBcf
Agenda:
1. New JIRA JDO-757 "Add @Repeatable to all annotations which can be repeated" https://issues.apache.org/jira/browse/JDO-757
2. JDO-756 "Enhance PK to avoid LongIdentity/StringIdentity dependencies" https://issues.apache.org/jira/browse/JDO-756
3. JDO-751 "Support for Java8 Optional" https://issues.apache.org/jira/browse/JDO-751
4. JDO-735 "Make PersistenceManager and Query support AutoCloseable (JDK1.7+)" https://issues.apache.org/jira/browse/JDO-735
5. JDO-747 "Behavior of delete() with multiple concurrent Transactions" https://issues.apache.org/jira/browse/JDO-747
6. JDO 3.1: Need to go through change lists in JIRA for 3.1 RC1 and 3.1 to prepare JCP Change Log
7. 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>
Re: Minutes: JDO TCK Conference Call Friday October 28, 9 AM Pacific Daylight Time (PDT)
Posted by Craig Russell <cr...@oracle.com>.
> On Oct 28, 2016, at 10:34 AM, Andy Jefferson <an...@datanucleus.org> wrote:
>
>> 1. New JIRA JDO-757 "Add @Repeatable to all annotations which can be repeated" https://issues.apache.org/jira/browse/JDO-757
>>
>> Looks like we are almost done here. No need to deprecate existing “repeatable container” annotations. If any user really wants to use them, fine.
>
> Well there would be zero point in deprecating them since they are required for @Repeatable to work, hence they can never be deleted.
I did not realize this. Good to know.
>
>> Question:
>> why was ElementType.TYPE added to Column? What does this mean?
>
> Means that when @Column annotation was originally added it was incorrect. @Column on a class is to define "unmapped columns" to equate to <column> just under <class> in XML.
Apparently the unmapped column paradigm has exactly one use case:
/**
* Value to be inserted when this is an “unmapped” column
* @return the value to be inserted when this is an “unmapped” column
*/
String insertValue() default ““;
It looks like there is no tck test for this. Oh Well.
> When adding @Repeatable the compiler tells you about such errors so had to be fixed (so that the singular annotation with @Repeatable is consistent with the container annotation).
Looks good. I think we’re done here.
Craig
>
>
>
> Regards
> --
> Andy
> DataNucleus (Web: http://www.datanucleus.org Twitter: @datanucleus)
Craig L Russell
Architect
craig.russell@oracle.com
P.S. A good JDO? O, Gasp!
Re: Minutes: JDO TCK Conference Call Friday October 28, 9 AM Pacific Daylight Time (PDT)
Posted by Andy Jefferson <an...@datanucleus.org>.
> 1. New JIRA JDO-757 "Add @Repeatable to all annotations which can be repeated" https://issues.apache.org/jira/browse/JDO-757
>
> Looks like we are almost done here. No need to deprecate existing “repeatable container” annotations. If any user really wants to use them, fine.
Well there would be zero point in deprecating them since they are required for @Repeatable to work, hence they can never be deleted.
> Question:
> why was ElementType.TYPE added to Column? What does this mean?
Means that when @Column annotation was originally added it was incorrect. @Column on a class is to define "unmapped columns" to equate to <column> just under <class> in XML. When adding @Repeatable the compiler tells you about such errors so had to be fixed (so that the singular annotation with @Repeatable is consistent with the container annotation).
Regards
--
Andy
DataNucleus (Web: http://www.datanucleus.org Twitter: @datanucleus)
Minutes: JDO TCK Conference Call Friday October 28, 9 AM Pacific Daylight Time (PDT)
Posted by Craig Russell <cr...@oracle.com>.
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell
NOTE: Next week Europe goes off DST while the conference call is still on DST.
Agenda:
1. New JIRA JDO-757 "Add @Repeatable to all annotations which can be repeated" https://issues.apache.org/jira/browse/JDO-757
Looks like we are almost done here. No need to deprecate existing “repeatable container” annotations. If any user really wants to use them, fine.
Question:
why was ElementType.TYPE added to Column? What does this mean?
Everything else looks good.
2. JDO-756 "Enhance PK to avoid LongIdentity/StringIdentity dependencies" https://issues.apache.org/jira/browse/JDO-756
3. JDO-751 "Support for Java8 Optional" https://issues.apache.org/jira/browse/JDO-751
This JIRA looks complete. AI: Tilmann open a new JIRA for subqueries returning collections that might have methods isEmpty(), contains(), and size(). Currently the only tck tests for subqueries return aggregate scalars.
4. JDO-735 "Make PersistenceManager and Query support AutoCloseable (JDK1.7+)" https://issues.apache.org/jira/browse/JDO-735
AI Michael reopen this JIRA and comment on the Query.isClosed() and the semantics of close() applied to Query.
We need a test case that tests that close() is idempotent and is useable in the try-with-resources context.
Add to the javadoc of Query.close() that this method is identical to closeAll() and is intended only for use by the try-with-resources pattern of Java 7. It is not intended to be called by the application. The close method may be a hint to the implementation that this Query object might not be used again.
5. JDO-747 "Behavior of delete() with multiple concurrent Transactions" https://issues.apache.org/jira/browse/JDO-747
6. JDO 3.1: Need to go through change lists in JIRA for 3.1 RC1 and 3.1 to prepare JCP Change Log
7. Other issues
Chapter 14 tables are strangely formatted. Michael volunteered to make changes.
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!