Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell Agenda:
1. JDO-762 "setParameters and setNamedParameters should use thread local storage" https://issues.apache.org/jira/browse/JDO-762 If we retain the setParameters, setNamedParameters, setRange, and range methods we should make them thread-safe. Feedback from Andy? I would lean toward adding Object... parameter to the new execute methods. Also we could add a Map parameter to the new execute methods. Alternatively, we could say that in order to pass a Map of named parameters, it must be the only parameter object (used with the Object... parameter). Do we have any use case for a Map as a parameter? We can disallow this until a user comes up with an example and shows how the RI doesn't support it. Then we can reopen the issue. How to handle range? We can add LOW and HIGH as key values for the Map parameter. Define these in Constants and disallow their use as normal named parameters. If we make the key values something that would disallow them from normal parameters then there would not be a conflict. For example, in Constants.java: static String QUERY_MAP_PARAMETER_KEY_LOW_RANGE = "$LOW"; static String QUERY_MAP_PARAMETER_KEY_HIGH_RANGE = "$HIGH"; Another idea: abstract the parameter to a new class Query.ParameterHolder. This class could take Object... or Map as constructor values and have the setParameters and setRange methods operate on it. Then we could add execute methods taking ParameterHolder as an argument. Or if passed to the execute(Object... ) method, if the first and only actual parameter is a ParameterHolder then parameters are taken from it. AI Craig update the JIRA. 2. JDO-763 "RI does not implement default of Query.setResult" https://issues.apache.org/jira/browse/JDO-763 Andy has been assigned to this JIRA. 3. JDO-761 "Add TCK test running sample queries from the spec" https://issues.apache.org/jira/browse/JDO-761 Michael is updating the sample queries to call multiple versions of the execute methods. 4. JDO-760 "Spec update regarding whether Query.execute() returns List or Collection" https://issues.apache.org/jira/browse/JDO-760 5. Is anything still unresolved with JDO-749 "Support for java.time types, and querying using associated methods" https://issues.apache.org/jira/browse/JDO-749 6. Is anything still unresolved with JDO-745 "Support bitwise operations in JDOQL" https://issues.apache.org/jira/browse/JDO-745 7. 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 Craig plans to retire from Oracle. This will leave the specification lead position open. AI Craig resolve this with Oracle. Action Items from weeks past: [Apr 12 2017] AI Craig: write a test case to see how the RI behaves JDO-762. [Feb 24 2017] AI Michael: are there any TCK tests for the new methods JDO-749? [Feb 24 2017] AI Michael: are there any TCK tests for the new methods? Any additional spec updates JDO-745? [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.
