Minutes: JDO TCK meeting Tuesday October 8 1100 PDT 2000 CEST

[Tilmann Zäschke]

Attendees: Michael Bouschen, Tilmann Zäschke

Next Meeting: Tuesday October 15, 1100 PDT, 2000 CEST

Agenda:

1. Branch dependabot/maven/parent-pom/commons-io-commons-io-2.14.0 created

Merged. This appears to be a simple security update, all checks passed, 
consensus to merge.



2. JIRA JDO-843 "JDOQLTypedQuery: issue with candidate("this") method" 
https://issues.apache.org/jira/browse/JDO-843
- DN ticket #133 "JDOQLTypedQuery: wrong query result when replacing 
QFullTimeEmployee.candidate() by QFullTimeEmployee.candidate("this")"

https://github.com/datanucleus/datanucleus-api-jdo/issues/133
- New version 5.2.10 of datanucleus-jdo-api includes only part of the 
fixes proposed by Michael


The new 5.2.10 causes several tests to fail. Michael will provide a PR 
with fixes.



3. JIRA JDO-842 "Q class specification of candidate() method" 
https://issues.apache.org/jira/browse/JDO-842


4. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" 
https://issues.apache.org/jira/browse/JDO-812


5. sonarcloud issues

 * JIRA JDO-819 "Code quality analysis"
https://issues.apache.org/jira/browse/JDO-819
 * JIRA JDO-823 "Fix sonarcloud issues of type Code Smells"
https://issues.apache.org/jira/browse/JDO-823
 * Sonarcloud link: https://sonarcloud.io/summary/overall?id=db-jdo
 * Cognitive Complexity of methods should not be too high:
https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS3776&severities=CRITICAL&types=CODE_SMELL&id=db-jdo 


 * Raw types should not be used:
https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS3740&severities=MAJOR&id=db-jdo 



6. Other issues

Action Items from weeks past:

[Sep 10 2024] AI Craig: write up proposed changes in a new branch and 
send for review.
[Sep 03 2024] AI Craig: create a new branch in specification to track 
spec changes
[Aug 27 2024] AI JDO-842: propose PR for specification (query chapter) 
and API (javadoc) and TCK (query tests). Use branches JDO-842 for this 
work. The specification has its own repository.
[Jan 02 2024] AI everyone: see if anyone can see a problem with the 
parallel execution of tests Cast.java and SupportedOptionalMethods.java
[Jul 13 2023] AI All Open a new JIRA for Android since having JNDI in 
the API disallows use with Android
[Jun 08 2023] AI All make a JIRA: JDO support for Java Records 
https://openjdk.org/jeps/395
[Dec 09 2021] AI Craig: Try to contact all current/former participants 
in JDO development and see if and how they want to be recognized on the 
JDO and DB web sites.https://db.apache.org/whoweare.html
[Oct 07 2021] AI Craig send a private message to all JSR-243 Expert 
Group members asking if they wish to continue.
[Mar 25 2021] AI Craig: investigate "merging" papajdo and apache.clr 
accounts
[Oct 17 2014] AI Matthew any updates for "Modify specification to 
address NoSQL datastores "https://issues.apache.org/jira/browse/JDO-651

Re: Minutes: JDO TCK meeting Tuesday November 21 1100 PST 2000 CET

[Tilmann Zäschke]

Great, that works perfectly! :-)

On 21/11/2023 22:22, Michael Bouschen wrote:

Hi,


...

3. JDO-830: "tck: Migrate JUnit tests to version 5" 
https://issues.apache.org/jira/browse/JDO-830

PR #85 https://github.com/apache/db-jdo/pull/85

Still some issues with ConsoleLauncher writing to log files...
Good to merge. If still (color) issues with Console, another JIRA can 
be filed.


I found a way to disable the color in the junit result. The 
ConsoleLauncher has an option --disable-ansi-colors that does the job.


I checked in a change that makes use of option --disable-ansi-colors 
into the main branch. Please give it a try.


Regards Michael


Merged.

...

Re: Fwd: [apache/db-jdo] JDO-827 Simplify JNDI (PR #81)

[Tilmann Zäschke]

These are from four/five distinct events with 1-2 emails each: two 
commits, sonarcloud pass, the merge, and finally deleting the branch. 
(actually _four_  events, sonarcloud is trigger by commit I think)


One solution may be to have only the PR description in the header so 
that all emails concerning a single PR end up in the same thread. I 
doubt though that this is technically possible (or desirable).


Maybe we can stop Sonartype from sending emails? Or send them only if it 
actually fails?

I am also not sure why we get two emails for the merge.

Til


On 08/07/2023 01:33, Craig Russell wrote:

There are over half a dozen messages regarding JDO-827/PR#81.

Is there a problem with the asf.yaml configuration that prevents these from 
being threaded?

I know we updated asf.yaml recently but somehow this does not meet my 
expectations.

Thanks,
Craig


Begin forwarded message:

From: Tilmann 
Subject: Re: [apache/db-jdo] JDO-827 Simplify JNDI (PR #81)
Date: July 6, 2023 at 11:43:49 PDT
To: apache/db-jdo 
Cc: Subscribed 
Reply-To: apache/db-jdo 



Merged #81  into main.

—
Reply to this email directly, view it on GitHub 
, or unsubscribe 
.
You are receiving this because you are subscribed to this thread.


Craig L Russell
c...@apache.org

Re: Reschedule June 29 meeting?

[Tilmann Zäschke]

2100 CET works for me.

Best,
Til

On 27/06/2023 18:11, Craig Russell wrote:

I may have a conflict on Thursday June 29 at 1100/2000.

Can we reschedule the call for one hour later? Thursday June 29 1200 PDT 2100 
CET.

Thanks,
Craig

Craig L Russell
c...@apache.org

Re: Mailing list configurations for discussion

[Tilmann Zäschke]

https://community.apache.org/contributors/mailing-lists


That looks good to me. Since these are just .asf.yam setting, I suppose it 
should be easy to just try it out?

Best,
Til

On 18/05/2023 02:37, Craig Russell wrote:

Take a look at this:

https://community.apache.org/contributors/mailing-lists

It may make sense for us to re-examine our mail lists, notifications, etc.

WDYT?
Craig

Craig L Russell
c...@apache.org

Re: [db-jdo] 01/01: Update PropertyUtils.java

[Tilmann Zäschke]

I had the same problem (1.8.0-331 is not in the allowed range [11,).)

My simple workaround was to use Java 11 (or later) to run the tool.
You can also try autoformatting from your IDE, just check that it 
formats only what you want to be changed.


But I agree that we should probably discuss this:

- Is there a version of that tool that runs with Java 8?

- Alternatively, is it okay to say that we require Java 11 to DEVELOP 
the TCK while requiring Java 8 to RUN it?


Best,
Til


On 04.04.23 02:27, Craig Russell wrote:

Hi Tobias,

Thanks for the hint. I changed the javadoc for the two methods and tried again.

The error message wasn't helpful but I ran mvn locally and now get:

org.apache.maven.enforcer.rule.api.EnforcerRuleException: Detected JDK Version: 
1.8.0-331 is not in the allowed range [11,).
 
I have 1.8.361 installed according to the Java control panel (last updated today).

But my env has
JAVA_HOME /Library/Java/JavaVirtualMachines/jdk1.8.0_331.jdk/Contents/Home

I looked in my /Library/Java/JavaVirtualMachines and there is only the one VM 
installed there.

But that's just on my local machine. What is the problem with the GitHub runner?

I also found this from stackOverflow:

  clr% /usr/libexec/java_home -V
Matching Java Virtual Machines (2):
 1.8.361.09 (x86_64) "Oracle Corporation" - "Java" /Library/Internet 
Plug-Ins/JavaAppletPlugin.plugin/Contents/Home
 1.8.0_331 (x86_64) "Oracle Corporation" - "Java SE 8" 
/Library/Java/JavaVirtualMachines/jdk1.8.0_331.jdk/Contents/Home
/Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home

Any ideas?
Thanks,
Craig


On Apr 3, 2023, at 14:17, Tobias Bouschen 
 wrote:

Hi Craig,

the instructions on how to run the format jobs are given in the readme: 
https://github.com/apache/db-jdo#formatting-using-maven

GJF also formats javadoc. So my guess would be that the new javadoc is not formatted 
correctly. The issue is probably that the javadoc has a linebreak even though the 
character limit is not reached on the first line. If you want the second line to 
actually be printed as a second line in the javadoc, you have to add '' 
between the two lines. If you just add a blank line between the two javadoc lines, 
the formatter should do this for you.

Best regards,
Tobias

On 03/04/2023 22:25, Craig Russell wrote:

So the code format check failed. I cannot see anything wrong with the changes I 
made.

https://github.com/apache/db-jdo/actions/runs/4591159720/jobs/8107138939?pr=73

Error:  To fix formatting errors, run "mvn 
com.spotify.fmt:fmt-maven-plugin:format"
8275
  
Error:
  Non complying file: 
/home/runner/work/db-jdo/db-jdo/exectck/src/main/java/org/apache/jdo/exectck/PropertyUtils.java
While I try to figure out how to run com.spotify.fmt could anyone just tell me 
what the problem is?

Thanks,
Craig


Begin forwarded message:

From: c...@apache.org
Subject: [db-jdo] 01/01: Update PropertyUtils.java
Date: April 2, 2023 at 15:28:40 PDT
To: "jdo-comm...@db.apache.org" 
Reply-To: jdo-dev@db.apache.org

This is an automated email from the ASF dual-hosted git repository.

clr pushed a commit to branch clr-apache-array-copy
in repository https://gitbox.apache.org/repos/asf/db-jdo.git

commit 034060cb69ad0a10f9bdf5aca4d5a0c9c9c11e8c
Author: Craig L Russell 
AuthorDate: Sun Apr 2 15:28:34 2023 -0700

Update PropertyUtils.java

JDO-819 Fix code smells
Use "Arrays.copyOf", "Arrays.asList", "Collections.addAll" or 
"System.arraycopy" instead.
---
.../java/org/apache/jdo/exectck/PropertyUtils.java | 23 ++
1 file changed, 10 insertions(+), 13 deletions(-)

diff --git a/exectck/src/main/java/org/apache/jdo/exectck/PropertyUtils.java 
b/exectck/src/main/java/org/apache/jdo/exectck/PropertyUtils.java
index 07473bce..eef6d73c 100644
--- a/exectck/src/main/java/org/apache/jdo/exectck/PropertyUtils.java
+++ b/exectck/src/main/java/org/apache/jdo/exectck/PropertyUtils.java
@@ -16,6 +16,7 @@ package org.apache.jdo.exectck;
import java.io.File;
import java.io.FileInputStream;
import java.io.IOException;
+import java.util.Arrays;
import java.util.Collection;
import java.util.List;
import java.util.Properties;
@@ -28,31 +29,27 @@ public class PropertyUtils {
   }

   /**
-   * Separates white space separated items from a String into Collection 
entries Used to collect
-   * command line argument lists into a Collection
+   * Separates white space separated items from a String into a Set
+   * Used to collect command line arguments
*
* @param names String of white space separated items
-   * @param list HashSet to contain String items
+   * @param set Set to contain String items
*/
-  public static void string2Set(String names, Collection list) {
+  public static void string2Set(String names, Collection set) {
 String[] items = names.split("[ \t\n]");
-for (String s : items) {
-  list.add(s);
-}
+s

Re: JDO TCK Conference Call Thursday March 16 1200 PDT 2000 CET

[Tilmann Zäschke]

Sorry, just got the blue screen of death.

Next week Thursday is fine if you haven't decided yet...

Cheers, Til


On 15/03/2023 21:02, Michael Bouschen wrote:

Hi,

We will have our regular meeting Thursday March 16 12:00 Pacific 
Daylight Time (PDT) 20:00 Central European Time (CET) to discuss JDO 
TCK issues and status.


We use the following dial-in for audio and video:
https://us02web.zoom.us/j/87074698575?pwd=bmZXeVV3dVowRHFDWk9KWFdVWjc3dz09 



Agenda:

1. JIRA JDO-819 "Code quality analysis" 
https://issues.apache.org/jira/browse/JDO-819
   JIRA JDO-823 "Fix sonarcloud issues of type Code Smells" 
https://issues.apache.org/jira/browse/JDO-823


Sonarcloud link: https://sonarcloud.io/summary/overall?id=db-jdo

 * Standard outputs shoudl not be used to log anything:
https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS106&severities=MAJOR&types=CODE_SMELL&id=db-jdo
 * Unsed type parameters shoudl be removed:
https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS2326&severities=MAJOR&types=CODE_SMELL&id=db-jdo
 * Exception classes should be immutable:
https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS1165&severities=MINOR&types=CODE_SMELL&id=db-jdo
 * Arrays should be be copied using loops:
https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS3012&severities=MINOR&types=CODE_SMELL&id=db-jdo
 * Arrays should not be created for varargs parameters:
https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS3878&severities=MINOR&types=CODE_SMELL&id=db-jdo
 * Loops shoudl not contain more than a single "break" or "continue"
   statement:
https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS135&severities=MINORtypes=CODE_SMELL&id=db-jdo
 * Mutable fields sould not be "public static":
https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS2386&severities=MINOR&types=CODE_SMELL&id=db-jdo
 * Type parameter names should comply with naming convention:
https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS119&severities=MINOR&types=CODE_SMELL&id=db-jdo
 * Unused local variables should be removed:
https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS1481&severities=MINOR&types=CODE_SMELL&id=db-jdo

 * Cognitive Complexity of methods should not be too high:
https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS3776&severities=CRITICAL&types=CODE_SMELL&id=db-jdo

 * Raw types should not be used:
https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS3740&severities=MAJOR&id=db-jdo



2. JIRA JDO-709 "Standardize field/property converters" 
https://issues.apache.org/jira/browse/JDO-709


3. JIRA JDO-822: "Verify compatibility with JDK 20" 
https://issues.apache.org/jira/browse/JDO-822


4. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" 
https://issues.apache.org/jira/browse/JDO-812


5. Other issues

Action Items from weeks past:

[Nov 23 2022] AI Tilmann follow up with Andy/DataNucleus for his 
advice on JDO-709.
[Oct 20 2022] AI Craig update the JIRA JDO-709 to request a test case 
using annotations and results of the test.
[Dec 09 2021] AI Craig: Try to contact all current/former participants 
in JDO development and see if and how they want to be recognized on 
the JDO and DB web sites.https://db.apache.org/whoweare.html
[Oct 07 2021] AI Craig send a private message to all JSR-243 Expert 
Group members asking if they wish to continue.
[Mar 25 2021] AI Craig: investigate "merging" papajdo and apache.clr 
accounts
[Oct 17 2014] AI Matthew any updates for "Modify specification to 
address NoSQL datastores" https://issues.apache.org/jira/browse/JDO-651

Re: JDO TCK Conference Call Wednesday March 1 1200 PST 2100 CET

[Tilmann Zäschke]

I am getting "the host has another meeting in progress" ...?


On 01/03/2023 18:57, Tobias Bouschen wrote:

Hi all,

sorry for the short notice again, but I won't be able to attend 
today's conference call. I will see you all next week.


Best regards,
Tobias

On 28/02/2023 20:58, Michael Bouschen wrote:

Hi,

We will have our regular meeting Wednesday March 1 12:00 Pacific 
Standard Time (PST) 21:00 Central European Time (CET) to discuss JDO 
TCK issues and status.


We use the following dial-in for audio and video:
https://us02web.zoom.us/j/87074698575?pwd=bmZXeVV3dVowRHFDWk9KWFdVWjc3dz09 



Agenda:

1. JIRA JDO-819 "Code quality analysis" 
https://issues.apache.org/jira/browse/JDO-819
   JIRA JDO-823 "Fix sonarcloud issues of type Code Smells" 
https://issues.apache.org/jira/browse/JDO-823


Sonarcloud link: https://sonarcloud.io/summary/overall?id=db-jdo

 * Try-catch blocks should not be nested:
https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS1141&severities=MAJOR&id=db-jdo 


 * Utility classes should not habe public constructors:
https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS1118&severities=MAJOR&id=db-jdo 


 * Sections of code should not be commented out:
https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS125&severities=MAJOR&id=db-jdo 


 * Throwable and Error shoudl not be caught:
https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS1181&severities=MAJOR&id=db-jdo 


 * Constructors of an abstract" class should not be declared "public":
https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS5993&severities=MAJOR&id=db-jdo 


 * Cognitive Complexity of methods should not be too high:
https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS3776&severities=CRITICAL&types=CODE_SMELL&id=db-jdo 


 * Raw types should not be used:
https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS3740&severities=MAJOR&id=db-jdo 



2. JIRA JDO-709 "Standardize field/property converters" 
https://issues.apache.org/jira/browse/JDO-709


3. JIRA JDO-822: "Verify compatibility with JDK 20" 
https://issues.apache.org/jira/browse/JDO-822


4. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" 
https://issues.apache.org/jira/browse/JDO-812


5. Other issues

Action Items from weeks past:

[Nov 23 2022] AI Tilmann follow up with Andy/DataNucleus for his 
advice on JDO-709.
[Oct 20 2022] AI Craig update the JIRA JDO-709 to request a test case 
using annotations and results of the test.
[Dec 09 2021] AI Craig: Try to contact all current/former 
participants in JDO development and see if and how they want to be 
recognized on the JDO and DB web 
sites.https://db.apache.org/whoweare.html
[Oct 07 2021] AI Craig send a private message to all JSR-243 Expert 
Group members asking if they wish to continue.
[Mar 25 2021] AI Craig: investigate "merging" papajdo and apache.clr 
accounts
[Oct 17 2014] AI Matthew any updates for "Modify specification to 
address NoSQL datastores" https://issues.apache.org/jira/browse/JDO-651

Re: JDO TCK Conference Call Wednesday February 8 1200 PST 2100 CET

[Tilmann Zäschke]

Hi Michael,

in the minutes last week it said:

Next meeting: Thursday February 9 1200 PST 2100 CET

Is it Feb 8 or Feb 9?

If it is today, I cannot make it, I will simply join next week :-)

Til


On 08.02.23 08:41, Michael Bouschen wrote:

Hi,

We will have our regular meeting Wednesday February 8 12:00 Pacific 
Standard Time (PST) 21:00 Central European Time (CET) to discuss JDO 
TCK issues and status.


We use the following dial-in for audio and video:
https://us02web.zoom.us/j/87074698575?pwd=bmZXeVV3dVowRHFDWk9KWFdVWjc3dz09 



Agenda:

1. JIRA JDO-819 "Code quality analysis" 
https://issues.apache.org/jira/browse/JDO-819
   JIRA JDO-823 "Fix sonarcloud issues of type Code Smells" 
https://issues.apache.org/jira/browse/JDO-823


Sonarcloud link: https://sonarcloud.io/summary/overall?id=db-jdo

2. JIRA JDO-709 "Standardize field/property converters" 
https://issues.apache.org/jira/browse/JDO-709


3. JIRA JDO-822: "Verify compatibility with JDK 20" 
https://issues.apache.org/jira/browse/JDO-822


4. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" 
https://issues.apache.org/jira/browse/JDO-812


5. Other issues

Action Items from weeks past:

[Nov 23 2022] AI Tilmann follow up with Andy/DataNucleus for his 
advice on JDO-709.
[Oct 20 2022] AI Craig update the JIRA JDO-709 to request a test case 
using annotations and results of the test.
[Dec 09 2021] AI Craig: Try to contact all current/former participants 
in JDO development and see if and how they want to be recognized on 
the JDO and DB web sites.https://db.apache.org/whoweare.html
[Oct 07 2021] AI Craig send a private message to all JSR-243 Expert 
Group members asking if they wish to continue.
[Mar 25 2021] AI Craig: investigate "merging" papajdo and apache.clr 
accounts
[Oct 17 2014] AI Matthew any updates for "Modify specification to 
address NoSQL datastores" https://issues.apache.org/jira/browse/JDO-651

Re: JDO TCK Conference Call Thursday February 2 1100 PST 2000 CET

[Tilmann Zäschke]

Unfortunately I have to skip tomorrow, something came up.

Best,
Til

On 01/02/2023 21:06, Michael Bouschen wrote:

Hi,

We will have our regular meeting Thursday February 2 11:00 Pacific 
Standard Time (PST) 20:00 Central European Time (CET) to discuss JDO 
TCK issues and status.


We use the following dial-in for audio and video:
https://us02web.zoom.us/j/87074698575?pwd=bmZXeVV3dVowRHFDWk9KWFdVWjc3dz09 



Agenda:

1. JIRA JDO-819 "Code quality analysis" 
https://issues.apache.org/jira/browse/JDO-819
   JIRA JDO-823 "Fix sonarcloud issues of type Code Smells" 
https://issues.apache.org/jira/browse/JDO-823


Sonarcloud link: https://sonarcloud.io/summary/overall?id=db-jdo 



Some candidate code smells to be discussed:
https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS1948&severities=CRITICAL&id=db-jdo 

https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS2692&severities=CRITICAL&id=db-jdo 

https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS1192&severities=CRITICAL&id=db-jdo 

https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS1214&severities=CRITICAL&id=db-jdo 

https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS127&severities=MAJOR&id=db-jdo 

https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS112&severities=MAJOR&id=db-jdo 

https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS1185&severities=MINOR&id=db-jdo 

https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS1481&severities=MINOR&id=db-jdo 



2. JIRA JDO-709 "Standardize field/property converters" 
https://issues.apache.org/jira/browse/JDO-709


3. JIRA JDO-822: "Verify compatibility with JDK 20" 
https://issues.apache.org/jira/browse/JDO-822


4. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" 
https://issues.apache.org/jira/browse/JDO-812


5. Other issues

Action Items from weeks past:

[Nov 23 2022] AI Tilmann follow up with Andy/DataNucleus for his 
advice on JDO-709.
[Oct 20 2022] AI Craig update the JIRA JDO-709 to request a test case 
using annotations and results of the test.
[Dec 09 2021] AI Craig: Try to contact all current/former participants 
in JDO development and see if and how they want to be recognized on 
the JDO and DB web sites.https://db.apache.org/whoweare.html
[Oct 07 2021] AI Craig send a private message to all JSR-243 Expert 
Group members asking if they wish to continue.
[Mar 25 2021] AI Craig: investigate "merging" papajdo and apache.clr 
accounts
[Oct 17 2014] AI Matthew any updates for "Modify specification to 
address NoSQL datastores" https://issues.apache.org/jira/browse/JDO-651

Re: JDO 709 test case

[Tilmann Zäschke]

I submitted an issue here: 
https://github.com/datanucleus/datanucleus-api-jdo/issues/127


Best,
Til

On 29/01/2023 12:48, Tilmann Zäschke wrote:

Michael,

just to let you know, I got the Attribute test case working. I'll let 
you know if I hit any more issues. I will clean up and commit soon 
(hopefully).


I hope you haven't invested too much time yet...

Best,
Til

JDO 709 test case

[Tilmann Zäschke]

Michael,

just to let you know, I got the Attribute test case working. I'll let 
you know if I hit any more issues. I will clean up and commit soon 
(hopefully).


I hope you haven't invested too much time yet...

Best,
Til

Re: JDO TCK Conference Call Thursday January 5 1100 PST 2000 CET

[Tilmann Zäschke]

Has the meeting already started? I can't get in  ("The meeting host 
will let you in soon")





On 04/01/2023 22:21, Michael Bouschen wrote:

Hi,

We will have our regular meeting Thursday January 5 11:00 Pacific 
Standard Time (PST) 20:00 Central European Time (CET) to discuss JDO 
TCK issues and status.


We use the following dial-in for audio and video:
https://us02web.zoom.us/j/87074698575?pwd=bmZXeVV3dVowRHFDWk9KWFdVWjc3dz09 



Agenda:

1. JIRA JDO-819 "Code quality analysis" 
https://issues.apache.org/jira/browse/JDO-819
   JIRA JDO-823 "Fix sonarcloud issues of type Code Smells" 
https://issues.apache.org/jira/browse/JDO-823


2. JIRA JDO-709 "Standardize field/property converters" 
https://issues.apache.org/jira/browse/JDO-709


3. JIRA JDO-822: "Verify compatibility with JDK 20" 
https://issues.apache.org/jira/browse/JDO-822


4. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" 
https://issues.apache.org/jira/browse/JDO-812


5. Other issues

Action Items from weeks past:

[Nov 23 2022] AI Tilmann see what else is needed to have the analysis 
integrated into GitHub repo.
[Nov 23 2022] AI Tilmann follow up with Andy/DataNucleus for his 
advice on JDO-709.
[Oct 20 2022] AI Craig update the JIRA JDO-709 to request a test case 
using annotations and results of the test.
[Dec 09 2021] AI Craig: Try to contact all current/former participants 
in JDO development and see if and how they want to be recognized on 
the JDO and DB web sites.https://db.apache.org/whoweare.html
[Oct 07 2021] AI Craig send a private message to all JSR-243 Expert 
Group members asking if they wish to continue.
[Mar 25 2021] AI Craig: investigate "merging" papajdo and apache.clr 
accounts
[Oct 17 2014] AI Matthew any updates for "Modify specification to 
address NoSQL datastores" https://issues.apache.org/jira/browse/JDO-651


Regards Michael

Re: Unable to make October 13 JDO meeting

[Tilmann Zäschke]

Wednesday October 12 at noon PDT 21 CEDT


Works for me.

Best, Til


On 11/10/2022 18:47, Bouschen, Michael wrote:

Hi Craig,

we could have the meeting Wednesday October 12 at noon PDT 21 CEDT, in case 
that helps.

What do the others think?

Regards Michael


Hi,

Sorry for the late notice, but I have a doctor appointment basically all day on 
Thursday.

I expect to be available the following week pretty much any time.

Apologies,
Craig

Craig L Russell
c...@apache.org





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

E-Mail: michael.bousc...@akquinet.de
Web:   www.akquinet.de

Geschäftsführung: Martin Weber, Dr. Torsten Fink, Heinz Wilming
Amtsgericht Berlin HRB 86780 • USt.-Id. Nr.: DE 225 964 680

[Facebook]  
[XING]  
[LinkedIn]  
[Twitter]

Re: JDO TCK Conference Call Thursday September 15 11 PDT 20 CEST

[Tilmann Zäschke]

Dear all,

my apologies, but again something came up and I cannot make it tomorrow.

Regards,
Tilmann



On 14/09/2022 21:04, Michael Bouschen wrote:

Hi,

We will have our regular meeting Thursday September 15 11:00 Pacific 
Daylight Time (PDT) 20:00 Central European Summer Time (CEST) to 
discuss JDO TCK issues and status.


We use the following dial-in for audio and video. You need a Skype 
account to join.

https://join.skype.com/lKWOxZDu2O5U

Agenda:
1. JIRA JDO-818 "Use Google Java Style as the code format conventions 
for the JDO project" https://issues.apache.org/jira/browse/JDO-818
New PR #57 "Maven plugin using Google Java Formatter" 
https://github.com/apache/db-jdo/pull/57


2. PR #50 "Update pom.xml to change http to https" 
https://github.com/apache/db-jdo/pull/50
Relates JIRA "Change headers on source files to use https:// instead 
of http:// " https://issues.apache.org/jira/browse/JDO-815


3. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" 
https://issues.apache.org/jira/browse/JDO-812


4. Other issues

Action Items from weeks past:

[Jun 15 2022] AI Craig verify that changing the headers now passes the 
RAT test without any other changes.
[Dec 09 2021] AI Craig: Try to contact all current/former participants 
in JDO development and see if and how they want to be recognized on 
the JDO and DB web sites.https://db.apache.org/whoweare.html
[Oct 07 2021] AI Craig send a private message to all JSR-243 Expert 
Group members asking if they wish to continue.
[Mar 25 2021] AI Craig: investigate "merging" papajdo and apache.clr 
accounts
[Oct 17 2014] AI Matthew any updates for "Modify specification to 
address NoSQL datastores" https://issues.apache.org/jira/browse/JDO-651


Regards Michael

Re: Minutes: JDO TCK Conference Call Thursday August 25 11 PDT 20 CEST

[Tilmann Zäschke]

Dear all,

unfortunately I cannot attend tomorrow. See you all next week.

Best,
Til


On 25/08/2022 21:06, Craig Russell wrote:

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

Next meeting: Thursday September 1 1100 PDT 2000 CEDT

Agenda:

1. JIRA JDO-817 "Check Compiler warnings" 
https://issues.apache.org/jira/browse/JDO-817
see PR 54 "Update pom.xml to show compiler warnings" 
https://github.com/apache/db-jdo/pull/54

No change since last week. Ready to merge?
Remove throws clause from Query and Extent close method
SingleFieldIdentity becomes a generic class so user-written subclasses are 
affected
README.md has a discussion of the warnings
Resolved: merge PR; change main branch to 3.3-SNAPSHOT. Squash/merge.

2. JIRA JDO-818 "Use Google Java Style as the code format conventions for the JDO 
project" https://issues.apache.org/jira/browse/JDO-818
see PR #55 "GJF reformat" https://github.com/apache/db-jdo/pull/55
see https://google.github.io/styleguide/javaguide.html

Proposal: run the tool on main (3.3-SNAPSHOT) after merging JDO-817. Discuss 
next time.
Question: is there any tool that allows for partial updates, e.g. only remove 
white space prior to line end. That might make it easier to review.

3. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" 
https://issues.apache.org/jira/browse/JDO-812

4. Other issues

Action Items from weeks past:

[Jun 15 2022] AI Craig verify that changing the headers now passes the RAT test 
without any other changes.
[Dec 09 2021] AI Craig: Try to contact all current/former participants in JDO 
development and see if and how they want to be recognized on the JDO and DB web 
sites.https://db.apache.org/whoweare.html
[Oct 07 2021] AI Craig send a private message to all JSR-243 Expert Group 
members asking if they wish to continue.
[Mar 25 2021] AI Craig: investigate "merging" papajdo and apache.clr accounts
[Oct 17 2014] AI Matthew any updates for "Modify specification to address NoSQL 
datastores" https://issues.apache.org/jira/browse/JDO-651

Craig L Russell
c...@apache.org

Re: JDO TCK Conference Call Thursday July 14 11 PDT 20 CEST

[Tilmann Zäschke]

@Michael Can you maybe leave and start it again? It just says "call
ended" on my side (from last week)


Til

On 14/07/2022 20:11, Bouschen, Michael wrote:

Hi,

no, I joinded the telecon and I'm still in.

Regards Michael

Hi,

has anyone else trouble joining the telecon?

Til


On 13/07/2022 20:39, Michael Bouschen wrote:
Hi,

We will have our regular meeting Thursday July 14 11:00 AM Pacific
Daylight Time (PDT) 20:00 Central European Summer Time (CEST) to
discuss JDO TCK issues and status.

We use the following dial-in for audio and video. You need a Skype
account to join.
https://mx.akquinet.de/link?id=BAgAAABUwTuQXAOm24EAAACNDz3zqISmHO20ogw45SRqmxBKHViOxbpGd0LItWooZKyl6bllk21NRXeW_uTxxWYNvHcHgg4pQUJyRjIcGVM0dJ2p67SHazUoRDgrB7fHBVQsY9NC-eEZE1vgxDL2ZJ0aVw4IxIht4NVvejRW_frKC8oOe5CsNP4f07KR6g77QSw1
Agenda:

1. JIRA JDO-817 "Check Compiler warnings"
https://issues.apache.org/jira/browse/JDO-817
see PR 54 "Update pom.xml to show compiler warnings"
https://github.com/apache/db-jdo/pull/54 and recent checkins into
branch tck-compiler-warnings

2. JIRA JDO-812 "Move to JDK 11 as the lowest supported version"
https://issues.apache.org/jira/browse/JDO-812
New comment from Andy about DataNucleus version v6.0 is supporting
Java11+.

3. Derby's removal of the security manager (see email from Tilmann)

4. Other issues

Action Items from weeks past:

[Jun 15 2022] AI Craig verify that changing the headers now passes the
RAT test without any other changes.
[Dec 09 2021] AI Craig: Try to contact all current/former participants
in JDO development and see if and how they want to be recognized on
the JDO and DB web sites.https://db.apache.org/whoweare.html
[Oct 07 2021] AI Craig send a private message to all JSR-243 Expert
Group members asking if they wish to continue.
[Mar 25 2021] AI Craig: investigate "merging" papajdo and apache.clr
accounts
[Oct 17 2014] AI Matthew any updates for "Modify specification to
address NoSQL datastores" https://issues.apache.org/jira/browse/JDO-651


Regards Michael



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

E-Mail: michael.bousc...@akquinet.de
Web:   www.akquinet.de

Geschäftsführung: Martin Weber, Dr. Torsten Fink, Heinz Wilming
Amtsgericht Berlin HRB 86780 • USt.-Id. Nr.: DE 225 964 680

[Facebook]  
[XING]  
[LinkedIn]  
[Twitter]

Re: JDO TCK Conference Call Thursday July 14 11 PDT 20 CEST

[Tilmann Zäschke]

When I try to start it it just does nothing.


On 14/07/2022 20:08, Craig Russell wrote:

I have not seen it start yet...


On Jul 14, 2022, at 11:07, Tilmann Zäschke  wrote:

Hi,

has anyone else trouble joining the telecon?

Til


On 13/07/2022 20:39, Michael Bouschen wrote:

Hi,

We will have our regular meeting Thursday July 14 11:00 AM Pacific
Daylight Time (PDT) 20:00 Central European Summer Time (CEST) to
discuss JDO TCK issues and status.

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

Agenda:

1. JIRA JDO-817 "Check Compiler warnings"
https://issues.apache.org/jira/browse/JDO-817
see PR 54 "Update pom.xml to show compiler warnings"
https://github.com/apache/db-jdo/pull/54 and recent checkins into
branch tck-compiler-warnings

2. JIRA JDO-812 "Move to JDK 11 as the lowest supported version"
https://issues.apache.org/jira/browse/JDO-812
New comment from Andy about DataNucleus version v6.0 is supporting
Java11+.

3. Derby's removal of the security manager (see email from Tilmann)

4. Other issues

Action Items from weeks past:

[Jun 15 2022] AI Craig verify that changing the headers now passes the
RAT test without any other changes.
[Dec 09 2021] AI Craig: Try to contact all current/former participants
in JDO development and see if and how they want to be recognized on
the JDO and DB web sites.https://db.apache.org/whoweare.html
[Oct 07 2021] AI Craig send a private message to all JSR-243 Expert
Group members asking if they wish to continue.
[Mar 25 2021] AI Craig: investigate "merging" papajdo and apache.clr
accounts
[Oct 17 2014] AI Matthew any updates for "Modify specification to
address NoSQL datastores" https://issues.apache.org/jira/browse/JDO-651


Regards Michael


Craig L Russell
c...@apache.org

Re: JDO TCK Conference Call Thursday July 14 11 PDT 20 CEST

[Tilmann Zäschke]

Hi,

has anyone else trouble joining the telecon?

Til


On 13/07/2022 20:39, Michael Bouschen wrote:

Hi,

We will have our regular meeting Thursday July 14 11:00 AM Pacific
Daylight Time (PDT) 20:00 Central European Summer Time (CEST) to
discuss JDO TCK issues and status.

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

Agenda:

1. JIRA JDO-817 "Check Compiler warnings"
https://issues.apache.org/jira/browse/JDO-817
see PR 54 "Update pom.xml to show compiler warnings"
https://github.com/apache/db-jdo/pull/54 and recent checkins into
branch tck-compiler-warnings

2. JIRA JDO-812 "Move to JDK 11 as the lowest supported version"
https://issues.apache.org/jira/browse/JDO-812
New comment from Andy about DataNucleus version v6.0 is supporting
Java11+.

3. Derby's removal of the security manager (see email from Tilmann)

4. Other issues

Action Items from weeks past:

[Jun 15 2022] AI Craig verify that changing the headers now passes the
RAT test without any other changes.
[Dec 09 2021] AI Craig: Try to contact all current/former participants
in JDO development and see if and how they want to be recognized on
the JDO and DB web sites.https://db.apache.org/whoweare.html
[Oct 07 2021] AI Craig send a private message to all JSR-243 Expert
Group members asking if they wish to continue.
[Mar 25 2021] AI Craig: investigate "merging" papajdo and apache.clr
accounts
[Oct 17 2014] AI Matthew any updates for "Modify specification to
address NoSQL datastores" https://issues.apache.org/jira/browse/JDO-651


Regards Michael

[ANNOUNCE] Apache JDO 3.2.1 released

[Tilmann Zäschke]

The Apache JDO project is pleased to announce a new release 3.2.1.

Java Data Objects (JDO) is a standard way to access persistent data in 
databases, using plain old Java objects (POJO) to represent persistent 
data.


JDO 3.2.1 can be obtained from the JDO download site:

http://db.apache.org/jdo/downloads.html.

JDO 3.2.1 is a bug fix release, notably :

* Compatibility with deprecated/removed SecurityManager in Java 18/19
* Schema descriptors have been moved to an Apache URL
* Removed compilation warnings when using Java 9

See the Release Notes of JDO 3.2.1 for details:
JDO 3.2.1: 
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12351329&styleName=Html&projectId=10630 



Please try out this new release.

[VOTE] [RESULTS] JDO 3.2.1 release

[Tilmann Zäschke]

Dear all,

JDO 3.2.1 (based on 3.2.1 RC2) has been approved as an official Apache 
JDO release. Thanks to

all who worked on the release and who voted.

+1
Craig Russell (pmc)
Michael Bouschen (pmc)
Tilmann Zäschke (pmc)
Tobias Bouschen (Committer)

There were no other votes.

Kind regards,
Til

Re: [VOTE] Please vote on JDO 3.2.1 release

[Tilmann Zäschke]

Can you verify your Java version with "java -version" and check 
JAVA_HOME and PATH / LD_LIBRARY_PATH (whatever it is on Mac)?


Also, is it expected to run "Internet Plug-Ins/JavaAppletPlugin.plugin"?

Til


On 25/05/2022 19:47, JDO Spec wrote:

Small problem with running the tests.

[ERROR] Failed to execute goal on project jdo-api: Could not resolve dependencies 
for project javax.jdo:jdo-api:jar:3.2.1-RC2: Could not find artifact 
com.sun:tools:jar:1.8.0 at specified path /Library/Internet 
Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/../lib/tools.jar -> [Help 1]
[ERROR]


Any ideas? I get the same thing with the main branch, so it's probably 
something in my local envt.

Thanks,
Craig


On May 22, 2022, at 07:28, Tilmann Zäschke  wrote:

Hi,

please vote on the JDO 3.2.1 release (based on RC2). Voting will be open until 
Wednesday,
May 25th, 14:30 UTC.

You may download the JDO 3.2.1 release artifacts from the staging repository:
https://repository.apache.org/content/repositories/orgapachejdo-1008/


The JDO API release artifacts are in
https://repository.apache.org/content/repositories/orgapachejdo-1008/javax/jdo/jdo-api/3.2.1-RC2/

The JDO TCK release artifacts are in
https://repository.apache.org/content/repositories/orgapachejdo-1008/org/apache/jdo/3.2.1-RC2/


For reference, changes since RC1 are:
- Cleaned up generation of LICENSE/NOTICE files (mbouschen)

Regards,
Til

Re: [VOTE] Please vote on JDO 3.2.1 release

[Tilmann Zäschke]

+1

Regards,
Tilmann

On 22/05/2022 16:28, Tilmann Zäschke wrote:

Hi,

please vote on the JDO 3.2.1 release (based on RC2). Voting will be 
open until Wednesday,

May 25th, 14:30 UTC.

You may download the JDO 3.2.1 release artifacts from the staging 
repository:

https://repository.apache.org/content/repositories/orgapachejdo-1008/


The JDO API release artifacts are in
https://repository.apache.org/content/repositories/orgapachejdo-1008/javax/jdo/jdo-api/3.2.1-RC2/ 



The JDO TCK release artifacts are in
https://repository.apache.org/content/repositories/orgapachejdo-1008/org/apache/jdo/3.2.1-RC2/ 




For reference, changes since RC1 are:
- Cleaned up generation of LICENSE/NOTICE files (mbouschen)

Regards,
Til

[VOTE] Please vote on JDO 3.2.1 release

[Tilmann Zäschke]

Hi,

please vote on the JDO 3.2.1 release (based on RC2). Voting will be open 
until Wednesday,

May 25th, 14:30 UTC.

You may download the JDO 3.2.1 release artifacts from the staging 
repository:

https://repository.apache.org/content/repositories/orgapachejdo-1008/


The JDO API release artifacts are in
https://repository.apache.org/content/repositories/orgapachejdo-1008/javax/jdo/jdo-api/3.2.1-RC2/

The JDO TCK release artifacts are in
https://repository.apache.org/content/repositories/orgapachejdo-1008/org/apache/jdo/3.2.1-RC2/ 




For reference, changes since RC1 are:
- Cleaned up generation of LICENSE/NOTICE files (mbouschen)

Regards,
Til

Please test staged JDO 3.2.1 release (RC1)

[Tilmann Zäschke]

Dear all,

I just staged JDO 3.2.1 RC1. Please have a look and report any problems:
https://repository.apache.org/content/repositories/orgapachejdo-1007/

Kind regards,
Tilmann

Re: [db-jdo-site] branch publish updated: Auto-deploy site for commit 54d547e22c

[Tilmann Zäschke]

Hi,

thanks for the update. Should we add some explanations what the columns
mean (DFG, PK, Persistent)?

Best,
Til



On 4/11/22 17:33, github-...@apache.org wrote:

This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a commit to branch publish
in repository https://gitbox.apache.org/repos/asf/db-jdo-site.git


The following commit(s) were added to refs/heads/publish by this push:
  new c5e13f8  Auto-deploy site for commit 54d547e22c
c5e13f8 is described below

commit c5e13f8abb245348ebe609291e28f6c76e44ab09
Author: andyjefferson 
AuthorDate: Mon Apr 11 15:33:40 2022 +

 Auto-deploy site for commit 54d547e22c
---
  content/field_types.html | 366 ++-
  1 file changed, 267 insertions(+), 99 deletions(-)

diff --git a/content/field_types.html b/content/field_types.html
index e3878b1..4c0f4e0 100644
--- a/content/field_types.html
+++ b/content/field_types.html
@@ -353,12 +353,17 @@ field of that type), whether the field is persisted by 
default (if it is
  to the field for it to be persisted by JDO), and whether the java type
  can be used as part of the primary key.
  
+
+Simple Types
+
+The following "simple" types are supported by default by the JDO spec.
+
  
  
+
+
  
-
-
-
+
  
  
  
@@ -418,362 +423,525 @@ can be used as part of the primary key.
  
  
  
-boolean[]
-
+java.lang.Boolean
+
+
+
+
+
+java.lang.Byte
+
+
+
+
+
+java.lang.Character
+
+
+
+
+
+java.lang.Double
+
  
  
  
  
-byte[]
+java.lang.Float
+
+
  
+
+
+java.lang.Integer
+
+
+
+
+
+java.lang.Long
+
+
+
+
+
+java.lang.Short
+
+
+
+
+
+java.lang.Number
+
  
  
  
  
-char[]
+java.lang.Object
+
  
-
  
  
  
-double[]
+java.lang.String
+
+
+
+
+
+java.math.BigDecimal
+
+
  
+
+
+java.math.BigInteger
+
+
  
+
+
+java.util.Currency
  
+
+
  
  
-float[]
+java.util.Locale
  
  
+
+
+
+java.lang.Enum
+
+
+
+
+
+java.lang.Optional
+
+
  
  
  
-int[]
+java.io.Serializable
+
  
-
  
  
  
-long[]
+javax.jdo.spi.PersistenceCapable
  
  
+
+
+
+
+
+
+Temporal Types
+
+The following temporal types are supported by default by the JDO spec.
+
+
+
+
+
+
+
+
+
+
+Java Type
+DFG?
+Persistent?
+PK?
+
+
+
+
+java.sql.Date
  
+
+
  
  
-short[]
+java.sql.Time
+
  
  
+
+
+java.sql.Timestamp
  
+
+
  
  
-java.lang.Boolean
+java.util.Date
  
  
  
  
  
-java.lang.Byte
+java.time.LocalDateTime
  
  
  
  
  
-java.lang.Character
+java.time.LocalTime
  
  
  
  
  
-java.lang.Double
+java.time.LocalDate
+
  
  
-
  
  
-java.lang.Float
+java.time.OffsetDateTime
+
  
  
-
  
  
-java.lang.Integer
+java.time.OffsetTime
  
  
  
  
  
-java.lang.Long
+java.time.MonthDay
  
  
  
  
  
-java.lang.Short
+java.time.YearMonth
  
  
  
  
  
-java.lang.Boolean[]
-
+java.time.Year
+
+
  
-
  
  
-java.lang.Byte[]
-
+java.time.Period
+
+
  
-
  
  
-java.lang.Character[]
-
+java.time.Instant
+
+
  
-
  
  
-java.lang.Double[]
-
+java.time.Duration
+
+
  
-
  
  
-java.lang.Float[]
-
+java.time.ZoneId
+
+
  
-
  
  
-java.lang.Integer[]
-
+java.time.ZoneOffset
+
+
  
-
  
  
-java.lang.Long[]
-
+java.time.ZonedDateTime
+
+
  
-
  
+
+
+
+
+Collection/Map Types
+
+The following "container" types are supported by default by the JDO spec, subject 
to the JDO implementation supporting that feature.
+
+
+
+
+
+
+
+
+
  
-java.lang.Short[]
+Java Type
+DFG?
+Persistent?
+PK?
+
+
+
+
+java.util.ArrayList
  
  
  
  
  
-java.lang.Number
-
+java.util.Collection
+
  
  
  
  
-java.lang.Object
-
+java.util.HashMap
  
+
  
  
  
-java.lang.String
-
-
+java.util.HashSet
+
  
+
  
  
-java.lang.String[]
+java.util.Hashtable
  
  
  
  
  
-java.math.BigDecimal
-
+java.util.LinkedHashMap
+
  
  
  
  
-java.math.BigInteger
-
-
+java.util.LinkedHashSet
+
  
+
  
  
-java.math.BigDecimal[]
+java.util.LinkedList
  
  
  
  
  
-java.math.BigInteger[]
+java.util.List
  
  
  
  
  
-java.sql.Date
-
+java.util.Map
  
  
+
  
  
-java.sql.Time
-
+java.util.Set
  
  
+
  
  
-java.sql.Timestamp
-
+java.util.TreeMap
  
  
+
  
  
-java.util.ArrayList
+java.util.TreeSet
  
  
  
  
  
-java.util.Collection
+java.util.Vector
  
  
  
  
+
+
+
+
+Array Types
+
+The vast majority of the "simple" SCO types can also be persisted as arrays of 
that type as well.
+
+
+
+
+
+
+
+
+
  
-java.util.Currency
+Java Type
+DFG?
+Persistent?
+PK?
+
+
+
+
+boolean[]
  
  
-
+
  
  
-java.util.Date
-
-
+byte[]
+
  
+
  
  
-java.util.Date[]
+char[]
  
  
  
  
  
-java.util.HashMap
+double[]
  
  
  
  
  
-java.util.HashSet
+float[]
  
  
  
  
  
-java.util.Hashtable
+int[]
  
  
  
  
  
-java.util.LinkedHashMap
+long[]
  
  
  
  
  
-java.util.LinkedHashSet
+short[]
  
  
  
  
  
-java.util.LinkedList
+java.lang.Boolean[]
  
  
  
  
  
-java.util.List
+java.lang.Byte[]
  
  
  
  
  
-java.util.Locale
+java.lang.Character[]
  
  
-
+
  
  
-java.util.Locale[]
+java.lang.Double[]
  
  
  
  
  
-java.util.Map
+java.lang.Float[]
  
  
  
  
  
-java.util.Set
+java.lang.Integer[]
  
  
  
  
  
-java.util.TreeMap
+

[ANNOUNCE] Apache JDO 3.2 released

[Tilmann Zäschke]

The Apache JDO project is pleased to announce a new release 3.2.

Java Data Objects (JDO) is a standard way to access persistent data in 
databases, using plain old Java objects (POJO) to represent persistent data.


JDO 3.2 can be obtained from the JDO download site:

http://db.apache.org/jdo/downloads.html.

JDO 3.2 has several new features, notably :

* New typesafe query API with generics
* Fluent query API allows chaining of query construction setters
* Support for Java "Time" and "Optional" fields in persistent classes 
and in queries
* Additional operations in query language with support for bit 
operations and additional Math operations.

* PersistenceManager and Query support AutoCloseable
* Baseline JDK is now JDK 1.8

In addition, JDO 3.2 contains many bug and documentation fixes and 
improvements.


See the Release Notes of JDO 3.2 for details:
JDO 3.2: 
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12316653&styleName=Html&projectId=10630 



Please try out this new release.

Derby, JDO, Torque websites missing

[Tilmann Zäschke]

Hi,

Updating the DB website succeeded, but the subproject websites
disappeared. I reported this here:
https://issues.apache.org/jira/browse/INFRA-22822

https://db.apache.org/

Any help is appreciated.

Best,
Til

[VOTE] Please vote on JDO 3.2 release

[Tilmann Zäschke]

Dear all,

I prepared the final release for JDO 3.2.

Please vote on the release. Voting will be open until Monday, January 31st.


You may download the JDO 3.2 release artifacts from the staging repository:
https://repository.apache.org/content/repositories/orgapachejdo-1006/

The JDO API release artifacts are in
https://repository.apache.org/content/repositories/orgapachejdo-1006/javax/jdo/jdo-api/3.2/


The JDO TCK release artifacts are in
https://repository.apache.org/content/repositories/orgapachejdo-1006/org/apache/jdo/3.2/

For reference, changes since the last vote are:
- Updated log4j from 2.13.3 to 2.17.1

Regards,
Til


On 02/12/2021 20:25, Tilmann wrote:

Hi,

after the cancelled vote for RC4 here is new request to vote:

Please vote on the JDO 3.2 release (based on RC5). Voting will be open
until Monday,
October 6th.

You may download the JDO 3.2 release artifacts from the staging
repository:
https://repository.apache.org/content/repositories/orgapachejdo-1005/

The JDO API release artifacts are in
https://repository.apache.org/content/repositories/orgapachejdo-1005/javax/jdo/jdo-api/3.2-RC5/



The JDO TCK release artifacts are in
https://repository.apache.org/content/repositories/orgapachejdo-1005/org/apache/jdo/3.2-RC5/



For reference, changes since RC4 are:
- Updated dependencies to latest 5.* versions of datanucleus modules
- Removed spec PDFs
- ReleaseHowTo.md updated


Regards,
Til

Fwd: [jira] [Comment Edited] (INFRA-22540) Change "Apache Rules" in Nexus to check for sha256/512 instead of sha1/md5

[Tilmann Zäschke]

Hi,

the INFRA ticket just got updated.

Could someone have a look whether I am describing the process/issue
correctly?

https://issues.apache.org/jira/browse/INFRA-22540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461830#comment-17461830

Thanks,
Til



 Forwarded Message 
Subject:[jira] [Comment Edited] (INFRA-22540) Change "Apache Rules" in
Nexus to check for sha256/512 instead of sha1/md5
Date:   Sat, 18 Dec 2021 10:26:00 + (UTC)
From:   Herve Boutemy (Jira) 
To: tilma...@apache.org




[
https://issues.apache.org/jira/browse/INFRA-22540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461830#comment-17461830
]
Herve Boutemy edited comment on INFRA-22540 at 12/18/21, 10:25 AM:
---

we had such discussion at Maven level: there is in general a confusion
between
1. Apache rules on source release to dist, which mandate sha256/sha512
2. Central rules on every artifacts (jar, pom, anything not related to
Apache source release), which still asks for sha1/md5 for checksums and
PGP signature for more serious checks

in Apache parent POM release 24 MPOM-244, we added a configuration to
generate sha512 for source-release artifacts when publishing to
Nexus/Central to help projects: see documentation
https://maven.apache.org/pom/asf/#The_apache-release_Profile

but not every project uses Apache parent POM, or did not upgrade to 24,
or do not even use Maven to build, so I don't know what's the best
solution for [~tilmannz]

at least, please consider the difference in policy of Apache source
release archive vs any other artifact published to Central if you change
something


was (Author: hboutemy):
we had such discussion at Maven level: there is in general a confusion
between
1. Apache rules on source release to dist, which mandate sha256/sha512
2. Central rules on every artifacts (jar, pom, anything not related to
Apache source release), which still asks for sha1/md5 for checksums and
PGP signature for more serious checks

in Apache parent POM release 24 MPOM-244, we added a configuration to
generate sha512 for source-release artifacts when publishing to
Nexus/Central to help projects: see documentation
https://maven.apache.org/pom/asf/#The_apache-release_Profile

but not every project uses Apache parent POM, or did not upgrade to 24,
or do not even use Maven to build, so I don't know what's the best
solution for [~tilmannz]

at least, please consider the difference in policy of Apache release
source release vs any artifact published to Central if you change something


Change "Apache Rules" in Nexus to check for sha256/512 instead of sha1/md5
--

Key: INFRA-22540
URL: https://issues.apache.org/jira/browse/INFRA-22540
Project: Infrastructure
Issue Type: Improvement
Components: Nexus
Reporter: Tilmann Zäschke
Priority: Major

The Release Distribution Policy
(https://infra.apache.org/release-distribution) states:
"PMCs must supply SHA-256 and/or SHA-512 and should not supply MD5 or
SHA-1.".
However, currently, the Apache Rules in Nexus appear to enforce that
all files (including .zip and .tar.gz) to have .sha1 and .md5
pendants. For our project "closing" a release candidate fails with:
Event: Failed: Checksum Validation
typeId checksum-staging
failureMessage Required SHA-1:
'/org/apache/jdo/3.2-RC3/jdo-3.2-RC3-source-release.zip.sha1'
failureMessage Required MD5:
'/org/apache/jdo/3.2-RC3/jdo-3.2-RC3-source-release.zip.md5'
failureMessage Required SHA-1:
'/org/apache/jdo/3.2-RC3/jdo-3.2-RC3-source-release.tar.gz.sha1'
failureMessage Required MD5:
'/org/apache/jdo/3.2-RC3/jdo-3.2-RC3-source-release.tar.gz.md5' Can
the Apache Rules in Nexus be adapted to allow or even enforce that
files (other than .jar/.pom) to be signed with sha256/sha512 instead
of sha1/md5?




--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Re: [VOTE] Please vote on JDO 3.2 release CANCELLED

[Tilmann Zäschke]

Dear all,

we have a new release candidate so this vote on RC4 is cancelled.

I will send out another email with a new vote for RC5.

Kind regards,
Til


On 25/11/2021 22:52, Tilmann wrote:

Hi,

Please vote on the JDO 3.2 release. Voting will be open until Monday,
November 29.

You may download the JDO 3.2 release artifacts from the staging
repository:
https://repository.apache.org/content/repositories/orgapachejdo-1004/


The JDO API release artifacts are in
https://repository.apache.org/content/repositories/orgapachejdo-1004/javax/jdo/jdo-api/3.2-RC4/


The JDO TCK release artifacts are in
https://repository.apache.org/content/repositories/orgapachejdo-1004/org/apache/jdo/3.2-RC4/


Regards,
Til

Re: JDO TCK Conference Call Thursday November 18 10:15 PST 19:15 CET

[Tilmann Zäschke]

Hi Craig,

apparently we missed each other by a few minutes only, we stuck around
until 20:07...

We discussed the INFRA issue.
One alternative would be to wait a few days, and if it doesn't look like
its going to be solved in the next week, we could just release RC4
anyway (RC3 is burnt), with sha512 where possible but without removing
any of the old md5/sha1. Anyone who wants can then use sha512, but we
could get the release out.

Or we wait for the ticket to be resolved as you suggested.
What do you think?

Til



On 18/11/2021 20:18, Craig Russell wrote:

Sorry gang,

I had the time wrong on my personal calendar so I missed the meeting.

I noticed the JIRA for Nexus.

Once the issue has been fixed and the RC3 closed, I have all I need to file the 
Maintenance Review with the JCP.

Craig


On Nov 17, 2021, at 12:11 PM, Michael Bouschen  wrote:

Hi,

We will have our regular meeting Thursday November 18 10:15 Pacific Standard 
Time (PST) 19:15 Central Europe to discuss JDO TCK issues and status.

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

Agenda:
1. JDO 3.2 release RC3
2. JDO-795 "Publishing the 3.2 
specification"https://issues.apache.org/jira/projects/JDO/issues/JDO-795
3. JSR-243 Maintenance Release
4. PR #34 "Revert "Pre 3.2 release fixes" 
https://github.com/apache/db-jdo/pull/34
5. PR #32 "3.2" https://github.com/apache/db-jdo/pull/32
6. Issues with Fix Version JDO-3.2 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20JDO%20AND%20fixVersion%20%3D%20%22JDO%203.2%22
7. Other issues

Action Items from weeks
[Nov 11 2021] AI Craig: send 3.2-RC3 artifacts to JCP for review.
[Oct 07 2021] AI Craig send a private message to all JSR-243 Expert Group 
members asking if they wish to continue.
[Sep 09 2021] AI Tobias pick a sample chapter to get an idea how much work it 
is to migrate specification to LaTeX
[Aug 05 2021] AI Craig contact JCP governance mavens
[Mar 25 2021] AI Craig: investigate "merging" papajdo and apache.clr accounts
[Jan 07 2021] AI Craig update to add workflow for contributions and preview of 
changes.
[Oct 30 2015] AI Craig: File a maintenance review with JCP
[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?
[Aug 24 2012] AI Craig update the JIRAs JDO-689 JDO-690 and JDO-692 about 
JDOHelper methods.

Regards Michael


Craig L Russell
c...@apache.org

Please test staged JDO 3.2 release (RC2)

[Tilmann Zäschke]

Dear all,

I just staged JDO 3.2 RC2. Please have a look and report any problems:
https://repository.apache.org/content/repositories/orgapachejdo-1002

Changes:
- archives are now available as .zip and as  .tar.gz
- the "source-release" archives are now signed with SHA512
- The pom now has the "timestamp" property
- Some updates on the release instructions

Note:
- The API is still signed with sha1 only. I believe this is in line with
the
  requirement of Nexus which does not seem to support SHA256 or SHA512.
- The parent .pom has its  section removed. It gets removed by the
  release plugin, not sure whether this is a feature or how it can be
avoided.
  I will add the section again after the release.

Kind regards,
Tilmann

Re: Is it worth establishing a separate mailing list for the GitHub message traffic?

[Tilmann Zäschke]

yes it does, we merged 4 (or 5?) PRs today, but I agree it is a bit noisy.

@Michael, should we put this on the agenda for next time?

tilmann



On 04/02/2021 21:29, Bryan Pendleton wrote:

Seems like the new website machinery generates a lot of messages?

bryan

-- Forwarded message -
From: GitBox 
Date: Thu, Feb 4, 2021 at 11:20 AM
Subject: [GitHub] [db-jdo-site] tzaeschke merged pull request #19:
Update pom.xml
To: 



tzaeschke merged pull request #19:
URL: https://github.com/apache/db-jdo-site/pull/19






This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

JDO-785 collaborative document

[Tilmann Zäschke]

Dear all,

Regarding JDO-785: I copied the file's content to a web-document so we may view 
and edit collaboratively next time (just a proposition, if you find that 
useful?):

https://docs.google.com/document/d/1rFZ_e4OZ4D8h208397iU9eQZaMjzlG1xWswojBW-2p4/edit?usp=sharing

I already made one change near the top.

Cheers,
Til


On 05/11/2020 20:33, Craig Russell wrote:

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

Next meeting: Thursday November 12 10:30 AM PST

Agenda:

1. JDO-785 "Update release instructions for new website and release process" 
https://issues.apache.org/jira/browse/JDO-785

AI All review the "how to release" page. Question: should we put this into the 
web site or leave it in the main repository? It's only useful for developers.

2. JDO-744 "XSD/DTD not published for JDO 3.1" 
https://issues.apache.org/jira/browse/JDO-744

3. JDO-709 "Standardize field/property converters" 
https://issues.apache.org/jira/browse/JDO-709

4. Issues with Fix Version JDO-3.2 
<https://issues.apache.org/jira/issues/?jql=project%20%3D%20JDO%20AND%20fixVersion%20%3D%20%22JDO%203.2%22%20ORDER%20BY%20status%20ASC>
5. Release Policy Updates
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

AI Craig update the web page for implementations to refer to DataNucleus 5.2 
and remove references to JDO 2.0 and 3.0.

Action Items from weeks past:
[Apr 22 2020] AI Andy fix page 
https://github.com/apache/db-jdo-site/blob/master/src/main/asciidoc/impls.adoc 
with latest DataNucleus implementations
[Feb 25 2020] AI Everyone review HowToReleaseJDO.md document: change svn to 
git; review all generated distribution files.
[Oct 30 2015] AI Craig: File a maintenance review with JCP
[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?
[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.

Craig L Russell
c...@apache.org

JUnit 5.7.0 vintage

[Tilmann Zäschke]

Hi Michael,

so the following worked mostly:


  org.junit.vintage
  junit-vintage-engine
  5.7.0


but if properly failed in the end with:

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-clean-plugin:3.1.0:clean (default-clean)
on project jdo: Failed to clean project: Failed to delete
C:\work\github\db-jdo\tck.txt -> [Help 1]

I usually get that as a warning, not as an error. But it may also
something wrong with my set-up.


Cheers,
Til

Shared simple document to draft new JDO website layout

[Tilmann Zäschke]

Dear all,

please have a look here:
https://docs.google.com/presentation/d/19RoED9sc2oAA1TrbENYNUwNPSnOU3P6Cd3DwvD4HqDY/edit?usp=sharing

I hope this is useful for drafting a new website layout.

Cheers,
Til

JDO-712 - SEQUENCE/SCHEMA default names

[Tilmann Zäschke]

Hi,

After the last telecon (that I attended) I had a look at various DBMS
for their handing of SEQUENCEs and schema
spaces.

If I remember correctly, the question in the telecon was to see which
DBMS support schema names for sequences.
I am a bit unclear now how this relates to the ticket, anyway, here is
what I found:

Postgres, Oracle and SQL Server allow creating sequences with optional
schema name: [schema_name.]sequence_name
MariaDB and DB2 do not appear to support schema names for sequences.
MySQL ans SQLite do not appear to support named sequences.

Some Object DBMS (such as ObjectDB) support named sequences via JPA
(@GeneratedValue/@SequenceGenerator).
As I understand, there is no way to create/use sequences without
attaching them to a Java field (=column in a table), so they are
implicitly bound to a table/schema.

No-SQL databases such as MongoDB, CouchDB or Cassandra do not really
support sequences as such, ie they clearly discourage their use even if
suported.

Also, DataNucleus:
http://www.datanucleus.org/products/datanucleus/jdo/mapping.html#valuegen_sequence


There seems to be no standard naming convention, except that the schema
name, if present, is separated by a '.' from from the sequence name.

Ticket: https://issues.apache.org/jira/browse/JDO-712

Kind regards,

Til

Re: JDO SVN repository

[Tilmann Zäschke]

Thanks, it appears to be working again, must have been something 
temporary... (?). Like last the last time.


Thanks,

Til


On 14.11.2017 08:07, Michael Bouschen wrote:

Hi,

it is working for me. the web-view
(https://svn.apache.org/viewvc/db/jdo) is also working. Network or
firewall issue?

2 trunk > svn up
Updating '.':
At revision 1815188.
3 trunk > svn info
Path: .
Working Copy Root Path: /Users/mbouschen/Projects/JDO/workspace/jdo
URL: https://svn.apache.org/repos/asf/db/jdo/trunk
Relative URL: ^/db/jdo/trunk
Repository Root: https://svn.apache.org/repos/asf
Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68
Revision: 1815188
Node Kind: directory
Schedule: normal
Last Changed Author: mbo
Last Changed Rev: 1814610
Last Changed Date: 2017-11-08 19:01:38 +0100 (Mi, 08 Nov 2017)

Regards Michael

svn up
Updating '.':
U
tck/src/java/org/apache/jdo/tck/query/jdoql/operators/BitwiseBinaryOperators.java
Updated to revision 1815145.
[MacBook-Pro-9:~/apache/jdo/trunk] clr% date
Mon Nov 13 14:35:47 PST 2017
[MacBook-Pro-9:~/apache/jdo/trunk] clr% svn info
Path: .
Working Copy Root Path: /Users/clr/apache/jdo
URL: https://svn.apache.org/repos/asf/db/jdo/trunk
Relative URL: ^/db/jdo/trunk
Repository Root: https://svn.apache.org/repos/asf
Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68
Revision: 1815145
Node Kind: directory
Schedule: normal
Last Changed Author: mbo
Last Changed Rev: 1814610
Last Changed Date: 2017-11-08 10:01:38 -0800 (Wed, 08 Nov 2017)



On Nov 13, 2017, at 12:28 PM, Tilmann Zäschke  wrote:

Hi,

is anyone else having trouble accessing the JDO SVN repo?

Neither SVN checkout on console nor the web-view (https://svn.apache.org/viewvc/db/jdo) 
appears to work, they just hang: "The server at svn.apache.org is taking too long to 
respond."

I first tried yesterday, but it is still not working for me...

Does it work for everybody else?

Cheers,
Tilmann


On 07.11.2017 19:30, Michael Bouschen wrote:

Hi,

We will have our regular meeting Thursday, November 8 at 9:30 AM Pacific Time 
(PST) 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-765 "TCK should fail if tests fail" 
https://issues.apache.org/jira/browse/JDO-765
2. JDO-764 "Allow JDO annotations to be used in meta-annotations" 
https://issues.apache.org/jira/browse/JDO-764
3. JDO-745 "Support bitwise operations in JDOQL" 
https://issues.apache.org/jira/browse/JDO-745
4. Remark from Andy about having the TCK runnable on other RDBMS.
5. TCK lifecycle tests fail.
6. Need to resolve specification lead issue now that Craig is no longer working 
for Oracle.
6. JDO 3.1: Need to go through change lists in JIRA for 3.1 RC1 and 3.1 to 
prepare JCP Change Log
8. Other issues

Action Items from weeks past:

[Nov 2  2017] AI Andy were the tck tests run after changes to DataNucleus?
[Oct 5  2017] AI Craig file a new JIRA about having the TCK runnable on other 
RDBMS
[Oct 30 2015] AI Craig: File a maintenance review with JCP
[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


Craig L Russell
Secretary, Apache Software Foundation
c...@apache.org http://db.apache.org/jdo

JDO SVN repository

[Tilmann Zäschke]

Hi,

is anyone else having trouble accessing the JDO SVN repo?

Neither SVN checkout on console nor the web-view 
(https://svn.apache.org/viewvc/db/jdo) appears to work, they just hang: 
"The server at svn.apache.org is taking too long to respond."


I first tried yesterday, but it is still not working for me...

Does it work for everybody else?

Cheers,
Tilmann


On 07.11.2017 19:30, Michael Bouschen wrote:

Hi,

We will have our regular meeting Thursday, November 8 at 9:30 AM Pacific Time 
(PST) 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-765 "TCK should fail if tests fail" 
https://issues.apache.org/jira/browse/JDO-765
2. JDO-764 "Allow JDO annotations to be used in meta-annotations" 
https://issues.apache.org/jira/browse/JDO-764
3. JDO-745 "Support bitwise operations in JDOQL" 
https://issues.apache.org/jira/browse/JDO-745
4. Remark from Andy about having the TCK runnable on other RDBMS.
5. TCK lifecycle tests fail.
6. Need to resolve specification lead issue now that Craig is no longer working 
for Oracle.
6. JDO 3.1: Need to go through change lists in JIRA for 3.1 RC1 and 3.1 to 
prepare JCP Change Log
8. Other issues

Action Items from weeks past:

[Nov 2  2017] AI Andy were the tck tests run after changes to DataNucleus?
[Oct 5  2017] AI Craig file a new JIRA about having the TCK runnable on other 
RDBMS
[Oct 30 2015] AI Craig: File a maintenance review with JCP
[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

Query compilation etc

[Tilmann Zäschke]

Hi,

a quick recap of the discussion we had in the last telecon. This was 
sparked by the discussion whether Query.compile() may need database 
access, i.e. whether it should fail when called outside transaction 
borders.


(TL;DR): See conclusion below.

Querying usually requires the following steps: query compilation 
(building an abstract syntax tree, query optimization and query execution.


Query compilation is rather simple, all it needs is knowledge of the 
database data model in order to verify compliance with the database schema.


Query optimization is usually more complicated, it can use static 
heuristics that are known on each client (table sizes, min/max values of 
indexes) but may also use information that is only available in the 
database. Information that is only available in the database included, 
for example, how many object does an index have in a given range. If one 
index has 4 objects and the other has 500, then using the first index 
may be the better choice.


JDO supports two separate steps: compilation and execution. The idea (as 
I understand) is to reuse queries efficiently by executing the 
compilation only once, while allowing to change parameters on compiled 
queries.


It seems that some query optimization can be done during the compilation 
step (such as removing redundant terms or choosing indexes based on 
static information, for example if there is only one index). Others, 
like choosing between different index, may depend on the actual 
parameters given and on the actual value distribution in a given index, 
as noted above.


It appears that query optimization could, and maybe should, be split 
into two parts. The first part is based on static information and can be 
performed during the compile() step. The second part may require 
database access, but may depends on the actual query parameters, so it 
will often be impossible to do this in the compilation step where the 
parameters may not be known. The second part can in many cases only be 
done during query execution.


Conclusion: At least for the optimizations that we considered, the 
current API works perfectly fine. Static optimization can be done during 
compile(), dynamic optimization can be done during execute(). This mean 
that compile() should work fine outside transactions boundaries.



Cheers,

Tilmann

Adding 'j...@apache.org' to lists.apache.org

[Tilmann Zäschke]

Hi,

I believe the 'j...@apache.org' list is missing from lists.apache.org . 
Could you please add it? I think it is meant to be public.


Cheers,
Tilmann (tilma...@apache.org)

JIRA 747

[Tilmann Zäschke]

Hi Andy,

(sorry for double posting, I sent this to an...@apache.org before)

I started looking into adapting datanucleus for JDO JIRA 747: 
https://issues.apache.org/jira/browse/JDO-747


Some time ago you offered to give some initial pointers, could you tell 
me where to start?


My first goal: Update datanuclues so that a PERSISTENT_NEW object 
transitions to PERSISTENT_CLEAN when they are refreshed _and_ if there 
is an object with the same ID in the database.


I tried to find the state transition checks and triggers. I first looked 
into datanucleus' Transaction.commit(), but it seems to forward 
everything to an implementation of XAResource.commit, probably either 
one of the LocalXAResource or the EmulatedXAResource classes. These 
forward the call to a 'Connection', but I can't immediately see which 
implementation is used.


Could you give me some pointers?

Thanks,
Tilmann

Re: EmbeddedPCMapping cannot be cast to PersistableMapping

[Tilmann Zäschke]

Hi,
I improved the TCK-test for Optional.

With the latest datanucleus (5.0.0-release-SNAPSHOT) there is are some 
problems remaining:


1) "SELECT FROM org.apache.jdo.tck.pc.query.OptionalSample WHERE 
!(optionalPC.optionalPC.isPresent())"


I think this should only return an object A if A references an object B 
where B does not reference anything else.
However, it also returns objects A where A do not reference anything 
else (reference is not present).



2) All the orElse() tests still fail. I fixed a number of errors in the 
tests, but I believe the tests are now correct.


I'll upload the latest version in a minute.

Best regards,
Tilmann


On 04-Jun-16 15:30, Andy Jefferson wrote:

Hi,


a) SQLSyntaxErrorException : Encountered "NOT" at line 1, column 185

Just seen your SQL generated. "WHERE NOT NOT (A0.OPTIONAL_PC IS NULL)"
That is valid on some RDBMS but maybe Derby is throwing its toys out of the 
pram due to it? Current DN code will put brackets in there. i.e NOT (NOT (...))



b) optionalPC.get().id

Released DN code only supports "optionalPC.get()" and not the access of fields 
of the dereferenced object (i.e it didn't do a join to the related table holding the 
object). Current DN code does however support that.
As I mentioned previously, if having problems use nightly builds.



c) Optional.orElse is currently not supported

Yes it is, and has been since DataNucleus v5.0.0-m4. You must be using an old 
version.

Regarding a use-case for orElse, the test I use is putting the orElse in the 
SELECT clause

Query q = pm.newQuery("SELECT id, stringField.orElse('NotPresent') FROM 
mydomain.MyClass");

so I get back the value that is stored when it is set, or some other value if 
not set (much like could be achieved with a CASE statement with other 
datatypes).



Regards

Re: EmbeddedPCMapping cannot be cast to PersistableMapping

[Tilmann Zäschke]

Hi,

I like the use case for orElse(), that looks indeed useful. I added a 
test case for that.



I switched to the latest m4-SNAPSHOT, that solves most of the problems.
Two problems remain:

a) Currently, "!(optionalPC.id == 88)" does not return objects with an 
'empty' optionalPC field.


I can't really tell whether this is correct or not. The spec says (14.6.2):
"Navigation through a null-valued field, which would throw 
NullPointerException, is treated as if the subexpression returned false."


If 'subexpression' means '!(optionalPC.id == 88)', the above behaviour 
is as intended.
However, so far (in ZooDB) I interpreted 'subexpression' as the 
'minimal' subexpression, i.e. 'optionalPC.id == 88' is the 
sub-expression. In this interpretation, the above query should also 
match all objects with an 'empty' optional field.


I'm not sure which is correct.

@Craig, @Michael, maybe you could clarify?


b) the first test in orElse() now accepts orElse(), but fails with a NPE:

testOrElse(org.apache.jdo.tck.query.jdoql.methods.SupportedOptionalMethods)java.lang.NullPointerException
at java.lang.Class.isAssignableFrom(Native Method)
at 
org.datanucleus.store.rdbms.sql.method.OptionalOrElseMethod.getExpression(OptionalOrElseMethod.java:61)
at 
org.datanucleus.store.rdbms.sql.expression.SQLExpressionFactory.invokeMethod(SQLExpressionFactory.java:306)
at 
org.datanucleus.store.rdbms.sql.expression.OptionalExpression.invoke(OptionalExpression.java:42)
at 
org.datanucleus.store.rdbms.query.QueryToSQLMapper.processInvokeExpression(QueryToSQLMapper.java:3711)
at 
org.datanucleus.store.rdbms.query.QueryToSQLMapper.processInvokeExpression(QueryToSQLMapper.java:3585)
at 
org.datanucleus.query.evaluator.AbstractExpressionEvaluator.compilePrimaryExpression(AbstractExpressionEvaluator.java:213)
at 
org.datanucleus.query.evaluator.AbstractExpressionEvaluator.compileUnaryExpression(AbstractExpressionEvaluator.java:182)
at 
org.datanucleus.query.evaluator.AbstractExpressionEvaluator.compileAdditiveMultiplicativeExpression(AbstractExpressionEvaluator.java:161)
at 
org.datanucleus.query.evaluator.AbstractExpressionEvaluator.compileRelationalExpression(AbstractExpressionEvaluator.java:136)
at 
org.datanucleus.query.evaluator.AbstractExpressionEvaluator.compileOrAndExpression(AbstractExpressionEvaluator.java:78)
at 
org.datanucleus.query.evaluator.AbstractExpressionEvaluator.evaluate(AbstractExpressionEvaluator.java:46)
at 
org.datanucleus.query.expression.Expression.evaluate(Expression.java:338)
at 
org.datanucleus.query.expression.DyadicExpression.evaluate(DyadicExpression.java:69)
at 
org.datanucleus.store.rdbms.query.QueryToSQLMapper.compileFilter(QueryToSQLMapper.java:553)
at 
org.datanucleus.store.rdbms.query.QueryToSQLMapper.compile(QueryToSQLMapper.java:429)
at 
org.datanucleus.store.rdbms.query.JDOQLQuery.compileQueryFull(JDOQLQuery.java:887)
at 
org.datanucleus.store.rdbms.query.JDOQLQuery.compileInternal(JDOQLQuery.java:347)

at org.datanucleus.store.query.Query.executeQuery(Query.java:1883)
at org.datanucleus.store.query.Query.executeWithArray(Query.java:1811)
at org.datanucleus.api.jdo.JDOQuery.executeInternal(JDOQuery.java:369)
at org.datanucleus.api.jdo.JDOQuery.executeWithArray(JDOQuery.java:268)
at org.apache.jdo.tck.query.QueryTest.execute(QueryTest.java:1257)
at org.apache.jdo.tck.query.QueryTest.execute(QueryTest.java:1133)
at 
org.apache.jdo.tck.query.QueryTest.executeAPIQuery(QueryTest.java:1069)
at 
org.apache.jdo.tck.query.jdoql.methods.SupportedOptionalMethods.checkQuery(SupportedOptionalMethods.java:297)
at 
org.apache.jdo.tck.query.jdoql.methods.SupportedOptionalMethods.testOrElse(SupportedOptionalMethods.java:312)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at org.apache.jdo.tck.JDO_Test.runBare(JDO_Test.java:284)
at 
org.apache.jdo.tck.util.BatchTestRunner.doRun(BatchTestRunner.java:108)
at 
org.apache.jdo.tck.util.BatchTestRunner.start(BatchTestRunner.java:148)
at 
org.apache.jdo.tck.util.BatchTestRunner.main(BatchTestRunner.java:123)



I'll upload the latest version to the JIRA.

Cheers,
Tilmann




On 04-Jun-16 15:30, Andy Jefferson wrote:

Hi,


a) SQLSyntaxErrorException : Encountered "NOT" at line 1, column 185

Just seen your SQL generated. "WHERE NOT NOT (A0.OPTIONAL_PC IS NULL)"
That is valid on some RDBMS but maybe Derby is throwing its toys out of the 
pram due to it? Current DN code will put brackets in there. i.e NOT (NOT (...))



b) optionalPC.get().id

Released DN code only supports "optionalPC.get()" and not the access of fields 
of the dereferenced object (i.e it didn't do a join to the related table holding the 
object). Current DN code does however support

Re: EmbeddedPCMapping cannot be cast to PersistableMapping

[Tilmann Zäschke]

The test mostly passes now. There are some issues, we should probably 
discuss them on Friday:


a)
SELECT FROM org.apache.jdo.tck.pc.query.OptionalSample WHERE 
!(optionalPC != null)

fails with
java.sql.SQLSyntaxErrorException: Syntax error: Encountered "NOT" at 
line 1, column 185


-> I think double negation is legal, would you agree?


b)
query #1=  "optionalPC.id == " + DUMMY_ID
query #2=  "optionalPC.get().id == " + DUMMY_ID
-> I think both queries should return the same result, but instead the 
second query returns the object with 'id=DUMMY_ID', not the one that 
refrerences the object with id=DUMMY_ID.


c) Optional.orElse is currently not supported. I think the proposal was 
to support this, but we discuss this on Friday:
"org.datanucleus.exceptions.NucleusUserException: Invocation of method 
"orElse" on "java.util.Optional" is not supported"



d) query: "optionalPC == null"
From this comment 
(https://issues.apache.org/jira/browse/JDO-751?focusedCommentId=15154475&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15154475) 
by Craig (Feb 19, 16:44) my understanding was that this should only 
return objects with 'optionalPC==null', but _not_ objects with 
'optionalPC.isEmpty()'.

However we can discuss this on Friday.

A related problem occurs with the query "!(optionalPC == null)"
This returns only objects where 'optionalPC.get() != null'.
My understanding was that it should also return with 
'optionalPC.isEmpty()', because the reference is not actually null.


From the post, my understanding was that we always assume 
optional-shortcut form when comparing to an actual instance, but allow 
comparison with the 'reference to Optional' when copmparing to 'null'.


Again, we can discuss this.

I'll upload a patch with the latest version.

Best,
Tilmann


On 31-May-16 20:33, Craig Russell wrote:

On May 31, 2016, at 3:08 AM, Tilmann Zäschke  wrote:

Hi,


More likely the problem is down to having a field as Optional

The test doesn't actually have Optional, but it does have:

Optional optionalAny;
Optional optionalNoGenerics;

I suppose these would not be allowed either (because they are mostly equivalent to 
Optional)?

Yes. Optional and Optional are not of much interest (to me at least).

I agree with Andy that supporting Object in an object model should be sufficiently 
flexible. Optional does not add any value to the model.

In plain English, "Object can be any object. Optional can be anything but 
with some special behavior about nullability"???

Craig

Regards,
Tilmann

On 31-May-16 11:53, Andy Jefferson wrote:

Hi,

thanks. Indeed it seems that the error is triggered by declaring a field
as 'Optional'.

That I doubt, due to established tests
https://github.com/datanucleus/tests/blob/master/jdo/general/src/test/org/datanucleus/tests/types/OptionalTest.java


More likely the problem is down to having a field as Optional, which is 
a minority interest use-case IMHO (which can often be symptomatic of a problem in a 
model, with lack of use of inheritance etc). Perhaps try nightly builds of jars if 
having problems.


Next step is likely to update the implementation.

DataNucleus has supported Optional since 5.0.0-m1, and tested on Optional<{basic}>, 
Optional (see link). It hasn't been tested on Optional where Object 
refers to potentially multiple types of PC.



Regards



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

Re: EmbeddedPCMapping cannot be cast to PersistableMapping

[Tilmann Zäschke]

Hi,


More likely the problem is down to having a field as Optional


The test doesn't actually have Optional, but it does have:

Optional optionalAny;
Optional optionalNoGenerics;

I suppose these would not be allowed either (because they are mostly 
equivalent to Optional)?


Regards,
Tilmann

On 31-May-16 11:53, Andy Jefferson wrote:

Hi,

thanks. Indeed it seems that the error is triggered by declaring a field
as 'Optional'.

That I doubt, due to established tests
https://github.com/datanucleus/tests/blob/master/jdo/general/src/test/org/datanucleus/tests/types/OptionalTest.java


More likely the problem is down to having a field as Optional, which is 
a minority interest use-case IMHO (which can often be symptomatic of a problem in a 
model, with lack of use of inheritance etc). Perhaps try nightly builds of jars if 
having problems.


Next step is likely to update the implementation.

DataNucleus has supported Optional since 5.0.0-m1, and tested on Optional<{basic}>, 
Optional (see link). It hasn't been tested on Optional where Object 
refers to potentially multiple types of PC.



Regards

Re: EmbeddedPCMapping cannot be cast to PersistableMapping

[Tilmann Zäschke]

Hi Craig,
thanks. Indeed it seems that the error is triggered by declaring a field 
as 'Optional'.
I thought I had seen an update note that 'Optional' would be supported 
by the latest milestone of DataNucleus, but I can't find it anymore.


I uploaded the patch to JIRA.
Next step is likely to update the implementation.

Cheers,
Tilmann

On 30-May-16 21:31, Craig Russell wrote:

Hi Tilmann,


On May 30, 2016, at 6:10 AM, Tilmann Zäschke  wrote:

Dear all,

I'm trying to implement the schema for the new Optional test, but I keep 
running into a ClassCastException:

javax.jdo.JDOFatalInternalException: Failed to generate new Mapping of type 
org.datanucleus.store.rdbms.mapping.java.OptionalMapping, exception : Failed to 
generate new Mapping of type 
org.datanucleus.store.rdbms.mapping.java.ObjectMapping, exception : 
org.datanucleus.store.rdbms.mapping.java.EmbeddedPCMapping cannot be cast to 
org.datanucleus.store.rdbms.mapping.java.PersistableMapping
java.lang.ClassCastException: 
org.datanucleus.store.rdbms.mapping.java.EmbeddedPCMapping cannot be cast to 
org.datanucleus.store.rdbms.mapping.java.PersistableMapping
at 
org.datanucleus.store.rdbms.table.ColumnCreator.createColumnsForField(ColumnCreator.java:253)
at 
org.datanucleus.store.rdbms.mapping.java.ReferenceMapping.createPerImplementationColumnsForReferenceField(ReferenceMapping.java:487)


I'm not mentioning 'embedded' anywhere, so I'm not sure where this assumption 
of 'embedding' comes from.

I think that Optional itself is treated as embedded. I’d investigate which field is causing 
the problem by trying, one at a time, Optional, Optional, 
etc. and see whether any of these is ok.

But is Optional even claimed to be supported by datanucleus? I haven’t seen any 
mail on the subject…

Craig



I do have Fields of type 'Object', but other tests also don't seem to require 
embedded=false or similar to handle field of type Object that reference PCs.

I'm also not even sure (or how I can find out) which of my mapping files are 
wrong. The error is the same for application-identity and datastore-identity. 
It occurs wile calling makePersistent().
I'm using the latest 'trunk' of the JDO TCK.

I also also consistently get the following error, but it seems to be a 
different issue:

Error copying implementation log file: Source 
'C:\Users\ztilmann\Desktop\projects\workspace-jdo\JDO\tck\datanucleus.txt' does 
not exist


Could anyone have a look and tell me what I'm doing wrong? I can also provide 
if the mistake is not obvious. Code snippets are below.

Cheers,
Tilmann


Code snippet (error occurs in last line in makePersistent):

@Override
protected void localSetUp() {
addTearDownClass(OptionalSample.class);
insertOptionalSample(getPM());
}

private void insertOptionalSample(PersistenceManager pm) {
Transaction tx = pm.currentTransaction();
try {
tx.begin();

//create a dummy object as target
OptionalSample dummyPC = new OptionalSample();
dummyPC.setId(DUMMY_ID);
pm.makePersistent(dummyPC);
...
}
}



Here are the schemas:

public class OptionalSample {
long id;

Optional optionalPC;
Optional optionalAny;
@SuppressWarnings("rawtypes")
Optional optionalNoGenerics;
Object any;

Optional optionalDate;
Optional optionalInteger;
Optional optionalString;

...
}


package.jdo
==


  
  
  
  
  
  
  
  
  
  
  



package-standard.orm:
=

   
  
  


  
  

  
  

  
  

  
  

  
  

  
  

  



schema.sql
==

CREATE TABLE OptionalSample (
ID INTEGER NOT NULL,
OPTIONAL_PC INTEGER REFERENCES SIMPLE_CLASS,
OPTIONAL_DATE DATE,
OPTIONAL_LONG BIGINT,
OPTIONAL_STRING VARCHAR(255),
OPTIONAL_ANY INTEGER REFERENCES SIMPLE_CLASS,
OPTIONAL_NO_GENERICS INTEGER REFERENCES SIMPLE_CLASS,
OBJECT_ANY INTEGER REFERENCES SIMPLE_CLASS,
CONSTRAINT OPTIONALSAMPLE_PK PRIMARY KEY (ID)
);


Full exception:
=

1) 
testParameterOptionalWithEmptyFields(org.apache.jdo.tck.query.jdoql.methods.SupportedOptionalMethods)javax.jdo.JDOFatalInternalException:
 Failed to generate new Mapping of type 
org.datanucleus.store.rdbms.mapping.java.OptionalMapping, exception : Failed to 
generate new Mapping of type 
org.datanucleus.store.rdbms.mapping.java.ObjectMapping, exception : 
org.datanucleus.store.rdbms.mapping.java.EmbeddedPCMapping cannot be cast to 
org.datanucleus.store.rdbms.mapping.java.PersistableMapping
java.lang.ClassCastException: 
org.datanucleus.store.rd

EmbeddedPCMapping cannot be cast to PersistableMapping

[Tilmann Zäschke]

Dear all,

I'm trying to implement the schema for the new Optional test, but I keep 
running into a ClassCastException:


javax.jdo.JDOFatalInternalException: Failed to generate new Mapping of 
type org.datanucleus.store.rdbms.mapping.java.OptionalMapping, exception 
: Failed to generate new Mapping of type 
org.datanucleus.store.rdbms.mapping.java.ObjectMapping, exception : 
org.datanucleus.store.rdbms.mapping.java.EmbeddedPCMapping cannot be 
cast to org.datanucleus.store.rdbms.mapping.java.PersistableMapping
java.lang.ClassCastException: 
org.datanucleus.store.rdbms.mapping.java.EmbeddedPCMapping cannot be 
cast to org.datanucleus.store.rdbms.mapping.java.PersistableMapping
at 
org.datanucleus.store.rdbms.table.ColumnCreator.createColumnsForField(ColumnCreator.java:253)
at 
org.datanucleus.store.rdbms.mapping.java.ReferenceMapping.createPerImplementationColumnsForReferenceField(ReferenceMapping.java:487)



I'm not mentioning 'embedded' anywhere, so I'm not sure where this 
assumption of 'embedding' comes from. I do have Fields of type 'Object', 
but other tests also don't seem to require embedded=false or similar to 
handle field of type Object that reference PCs.


I'm also not even sure (or how I can find out) which of my mapping files 
are wrong. The error is the same for application-identity and 
datastore-identity. It occurs wile calling makePersistent().

I'm using the latest 'trunk' of the JDO TCK.

I also also consistently get the following error, but it seems to be a 
different issue:
>> Error copying implementation log file: Source 
'C:\Users\ztilmann\Desktop\projects\workspace-jdo\JDO\tck\datanucleus.txt' 
does not exist



Could anyone have a look and tell me what I'm doing wrong? I can also 
provide if the mistake is not obvious. Code snippets are below.


Cheers,
Tilmann


Code snippet (error occurs in last line in makePersistent):

@Override
protected void localSetUp() {
addTearDownClass(OptionalSample.class);
insertOptionalSample(getPM());
}

private void insertOptionalSample(PersistenceManager pm) {
Transaction tx = pm.currentTransaction();
try {
tx.begin();

//create a dummy object as target
OptionalSample dummyPC = new OptionalSample();
dummyPC.setId(DUMMY_ID);
pm.makePersistent(dummyPC);
...
}
}



Here are the schemas:

public class OptionalSample {
long id;

Optional optionalPC;
Optional optionalAny;
@SuppressWarnings("rawtypes")
Optional optionalNoGenerics;
Object any;

Optional optionalDate;
Optional optionalInteger;
Optional optionalString;

...
}


package.jdo
==


  
  
  
  
  
  embedded="false"

field-type="org.apache.jdo.tck.pc.query.OptionalSample">
  
  persistence-modifier="persistent" embedded="false"

field-type="org.apache.jdo.tck.pc.query.OptionalSample">
  
  
  



package-standard.orm:
=

   
  
  


  
  

  
  

  
  

  
  

  
  

  
  

  



schema.sql
==

CREATE TABLE OptionalSample (
ID INTEGER NOT NULL,
OPTIONAL_PC INTEGER REFERENCES SIMPLE_CLASS,
OPTIONAL_DATE DATE,
OPTIONAL_LONG BIGINT,
OPTIONAL_STRING VARCHAR(255),
OPTIONAL_ANY INTEGER REFERENCES SIMPLE_CLASS,
OPTIONAL_NO_GENERICS INTEGER REFERENCES SIMPLE_CLASS,
OBJECT_ANY INTEGER REFERENCES SIMPLE_CLASS,
CONSTRAINT OPTIONALSAMPLE_PK PRIMARY KEY (ID)
);


Full exception:
=

1) 
testParameterOptionalWithEmptyFields(org.apache.jdo.tck.query.jdoql.methods.SupportedOptionalMethods)javax.jdo.JDOFatalInternalException: 
Failed to generate new Mapping of type 
org.datanucleus.store.rdbms.mapping.java.OptionalMapping, exception : 
Failed to generate new Mapping of type 
org.datanucleus.store.rdbms.mapping.java.ObjectMapping, exception : 
org.datanucleus.store.rdbms.mapping.java.EmbeddedPCMapping cannot be 
cast to org.datanucleus.store.rdbms.mapping.java.PersistableMapping
java.lang.ClassCastException: 
org.datanucleus.store.rdbms.mapping.java.EmbeddedPCMapping cannot be 
cast to org.datanucleus.store.rdbms.mapping.java.PersistableMapping
at 
org.datanucleus.store.rdbms.table.ColumnCreator.createColumnsForField(ColumnCreator.java:253)
at 
org.datanucleus.store.rdbms.mapping.java.ReferenceMapping.createPerImplementationColumnsForReferenceField(ReferenceMapping.java:487)
at 
org.datanucleus.store.rdbms.mapping.java.ReferenceMapping.prepareDatastoreMapping(ReferenceMapping.java:229)
at 
org.datanucleus.store.rdbms.mapping.java.ReferenceMapping.initialize(ReferenceMapping.java:104)
at 
org.datanucleus.store.rdbms.mapping.RDBMSMappingManager.getMapping(RDBMSMappingManager.java:482)
at 
org.datanucleus.store.rdbms.mapping.java.SingleCollectionMa

Re: A new general method to update object databases / Should it be included in Java Data Objects, JDO ?

[Tilmann Zäschke]

Hello Hei,
sorry, I posted my answer first only to the dev list, I'm not sure you 
are on it.

So here it is again, with some updates:


Hi,

I haven't read the whole post in detail, but I understand the main idea 
is garbage collection in databases. This reminds me of similar concepts 
in osome object databases, such as GemStone/Smalltalk 
(https://downloads.gemtalksystems.com/docs/GemStone64/3.3.x/GS64-ReleaseNotes-3.3/GS64-ReleaseNotes-3.3.htm). 
However, I'm not aware of any major Java-ODBMS that supports it.


Some comments:

- As Andy describes, it could be supported via a property of the PM. 
However, there may be scenarios when 'embed' and 'makePersistent' are 
regularily use in the same transaction, so if the feature would be 
widely used, it may make sense to have a dedicated 'embed' method.


- as far as I am aware, the JVM has moved away from reference counting. 
The situation in an DBMS may be different to an in-memory JVM, but if an 
ODBMS implements GC, it may be worth checking out other garbage 
collection techniques. One problem are reference cycles, I haven't read 
the full blogpost how this is solved.


- It seams that enabling garbage collection via reference counting will 
have quite some impact on performance, because objects get bigger 
(little impact) and because it requires updating of additional objects 
in the database to update the reference counters (the counters also need 
updating when _adding_ references). I would therefore argue that support 
for garbage collection should be determined at database creation time, 
or as a flag when defining database schema. This would allow avoiding 
the GC overhead when GC is not required.


- We would need to be able to identify root objects which should not be 
garbage collected. This could also be done via a flag on the schema, 
i.e. every object of a class that has no reference counters is 
automatically a root object.


Cheers,
Tilmann



On 13.05.2016 15:49, Andy Jefferson wrote:

Hi,

-I have invented a new declarative method to update object databases 
and I

would like to introduce that method you.

My question is:
Should the functionality of this method included in some future 
versions of

JDO (and perhaps some other definitions/systems under Apache)?
Also I am interested about your comments/critique on the method.

The name of the method is "embed" and it resembles the command
   pm.makePersistent(s);
used in JDO-enabled applications. The embed method is called in 
equivalent

way,
   db.embed(s);
but it has a larger functionality than the current makePersistent 
method.

My opinion/comments, others may have other thoughts :

For something to be part of JDO, it needs to be widely applicable 
across other datastores, not just for one "type" of datastore. If it 
is only implementable on 1 type of datastore then standardising it 
would be "premature"; that isn't to say that it isn't applicable to 
others.


 From what I read of your method it is basically a makePersistent 
(attach) but with "deleteOrphans" enabled; i.e it addresses the 
object graph defined by the input object, and additionally deletes 
orphaned objects. Firstly it is entirely reasonable to be able to do 
that right now in terms of API (**assuming the JDO implementation 
provided the internals**) since the user can call pm.makePersistent 
and can have set properties on the PersistenceManager just before 
that call (pm.setProperty(...), so can set some "deleteOrphans" 
flag). From that I can conclude that I don't think there would be any 
change to the API needed to provide your mode of operation.


Deleting orphans may vary dependent on the precise relation, hence 
why JDO allows metadata on each field, so some orphans can be deleted 
and others not.


Clearly a JDO implementation would need to provide a "deleteOrphans" 
mode internally to support this.


Detail of how your method works in an object database, whilst 
interesting, is not of relevance to the JDO spec question, since the 
spec doesn't define HOW an implementation implements features



Regards