Re: JDO TCK Conference Call Thursday July 1 11:00 AM Pacific Daylight Time (PDT)

[Michael Bouschen]

HI,
> Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
>
> Next meeting: Thursday July 22 11:00 Pacific
>
> Agenda:
>
> Question: Should we keep the change bars in the specification after we 
> publish 3.2? It would be easier to find the changes. But it's too late for 
> 3.2.
>
> 1. New db-jdo pull request #25  
>
> Good to go with changes now accepted.
>
> What happened to Table 15 in Chapter 6?


I found the missing figure 15.0 in a previous version of
Ch06-PersistentObjectModel.odt and added it back to the chapter.

Regards Michael


>
> 2. JDO-709 "Standardize field/property converters" 
> 
>
> AI Craig review all comments and close if they are all resolved.
>
> 3. Issues with Fix Version JDO-3.2 
> 
> 4. Open Issues w/o Fix Version 
> 
> 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
>
> Action Items from weeks
> [Mar 25 2021] AI Craig: investigate "merging" papajdo and apache.clr accounts
> [Feb 04 2021] AI Craig ask Oracle for license for the specification.
> [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?
> [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
>

[jira] [Updated] (JDO-795) Publishing the 3.2 specification

[Michael Bouschen (Jira)]

 [ 
https://issues.apache.org/jira/browse/JDO-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Bouschen updated JDO-795:
-
Description: 
* Added A.21 Changes for 3.1 and A.22 Changes for 3.2 to 
AppF-RevisionHistory.odt (done)
 * Added missing paragraphs about if-else expressions in JDOQL to 
Ch14-Query.odt  (done)

The following files still have change bars:  (done)
 * AppG-XML_Schema_jdoconfig.odt
 * AppH-XML_Schema_jdo.odt
 * AppI-XML_Schema_jdoqlquery.odt
 * AppJ-XML_Schema_orm.odt
 * Ch05-LifeCycle.odt
 * Ch14-Query.odt (from the changes above)

In Ch06 Figure 15 is missing.

Change the header: Java Data Objects 3.1 -> Java Data Objects 3.2

Change the footer: March 20, 2015 -> to the JDO 3.2 date

  was:
* Added A.21 Changes for 3.1 and A.22 Changes for 3.2 to 
AppF-RevisionHistory.odt (checked in)
 * Added missing paragraphs about if-else expressions in JDOQL to 
Ch14-Query.odt  (checked in)

The following files still have change bars:  (checked in)
 * AppG-XML_Schema_jdoconfig.odt
 * AppH-XML_Schema_jdo.odt
 * AppI-XML_Schema_jdoqlquery.odt
 * AppJ-XML_Schema_orm.odt
 * Ch05-LifeCycle.odt
 * Ch14-Query.odt (from the changes above)

In Ch06 Figure 15 is missing.


> Publishing the 3.2 specification
> 
>
> Key: JDO-795
> URL: https://issues.apache.org/jira/browse/JDO-795
> Project: JDO
>  Issue Type: Task
>  Components: specification
>Affects Versions: JDO 3.2
>Reporter: Michael Bouschen
>Priority: Major
> Fix For: JDO 3.2
>
>
> * Added A.21 Changes for 3.1 and A.22 Changes for 3.2 to 
> AppF-RevisionHistory.odt (done)
>  * Added missing paragraphs about if-else expressions in JDOQL to 
> Ch14-Query.odt  (done)
> The following files still have change bars:  (done)
>  * AppG-XML_Schema_jdoconfig.odt
>  * AppH-XML_Schema_jdo.odt
>  * AppI-XML_Schema_jdoqlquery.odt
>  * AppJ-XML_Schema_orm.odt
>  * Ch05-LifeCycle.odt
>  * Ch14-Query.odt (from the changes above)
> In Ch06 Figure 15 is missing.
> Change the header: Java Data Objects 3.1 -> Java Data Objects 3.2
> Change the footer: March 20, 2015 -> to the JDO 3.2 date



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: JDO TCK Conference Call Thursday July 1 11:00 AM Pacific Daylight Time (PDT)

[Craig Russell]

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

Next meeting: Thursday July 22 11:00 Pacific

Agenda:

Question: Should we keep the change bars in the specification after we publish 
3.2? It would be easier to find the changes. But it's too late for 3.2.

1. New db-jdo pull request #25  

Good to go with changes now accepted.

What happened to Table 15 in Chapter 6?

2. JDO-709 "Standardize field/property converters" 


AI Craig review all comments and close if they are all resolved.

3. Issues with Fix Version JDO-3.2 

4. Open Issues w/o Fix Version 

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

Action Items from weeks
[Mar 25 2021] AI Craig: investigate "merging" papajdo and apache.clr accounts
[Feb 04 2021] AI Craig ask Oracle for license for the specification.
[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?
[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

[jira] [Updated] (JDO-795) Publishing the 3.2 specification

[Michael Bouschen (Jira)]

 [ 
https://issues.apache.org/jira/browse/JDO-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Bouschen updated JDO-795:
-
Description: 
* Added A.21 Changes for 3.1 and A.22 Changes for 3.2 to 
AppF-RevisionHistory.odt (checked in)
 * Added missing paragraphs about if-else expressions in JDOQL to 
Ch14-Query.odt  (checked in)

The following files still have change bars:  (checked in)
 * AppG-XML_Schema_jdoconfig.odt
 * AppH-XML_Schema_jdo.odt
 * AppI-XML_Schema_jdoqlquery.odt
 * AppJ-XML_Schema_orm.odt
 * Ch05-LifeCycle.odt
 * Ch14-Query.odt (from the changes above)

In Ch06 Figure 15 is missing.

  was:
* Added A.21 Changes for 3.1 and A.22 Changes for 3.2 to 
AppF-RevisionHistory.odt
 * Added missing paragraphs about if-else expressions in JDOQL to Ch14-Query.odt

The following files still have change bars:
 * AppG-XML_Schema_jdoconfig.odt
 * AppH-XML_Schema_jdo.odt
 * AppI-XML_Schema_jdoqlquery.odt
 * AppJ-XML_Schema_orm.odt
 * Ch05-LifeCycle.odt
 * Ch14-Query.odt (from the changes above)


> Publishing the 3.2 specification
> 
>
> Key: JDO-795
> URL: https://issues.apache.org/jira/browse/JDO-795
> Project: JDO
>  Issue Type: Task
>  Components: specification
>Affects Versions: JDO 3.2
>Reporter: Michael Bouschen
>Priority: Major
> Fix For: JDO 3.2
>
>
> * Added A.21 Changes for 3.1 and A.22 Changes for 3.2 to 
> AppF-RevisionHistory.odt (checked in)
>  * Added missing paragraphs about if-else expressions in JDOQL to 
> Ch14-Query.odt  (checked in)
> The following files still have change bars:  (checked in)
>  * AppG-XML_Schema_jdoconfig.odt
>  * AppH-XML_Schema_jdo.odt
>  * AppI-XML_Schema_jdoqlquery.odt
>  * AppJ-XML_Schema_orm.odt
>  * Ch05-LifeCycle.odt
>  * Ch14-Query.odt (from the changes above)
> In Ch06 Figure 15 is missing.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [db-jdo] mboapache merged pull request #25: Jdo 795

[GitBox]

mboapache merged pull request #25:
URL: https://github.com/apache/db-jdo/pull/25


   


-- 
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.

To unsubscribe, e-mail: jdo-dev-unsubscr...@db.apache.org

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

[jira] [Closed] (JDO-782) Initially deferred constraint should be removed from BaseDatastoreAdapter instead of child classes

[Andy Jefferson (Jira)]

 [ 
https://issues.apache.org/jira/browse/JDO-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy Jefferson closed JDO-782.
--
Resolution: Invalid

Nothing to do with the Apache JDO project

> Initially deferred constraint should be removed from BaseDatastoreAdapter 
> instead of child classes
> --
>
> Key: JDO-782
> URL: https://issues.apache.org/jira/browse/JDO-782
> Project: JDO
>  Issue Type: Improvement
>Reporter: László Bodor
>Priority: Major
>
> It seems like only Oracle supports initially deferred constraints, so it 
> would make sense to remove it from BaseDatastoreAdapter instead of removing 
> it from every single subclass, and adding it only to OracleAdapter.
> My original issue was that Datanucleus generated initially deferred 
> constraints for MariaDB because it used BaseDatastoreAdapter. However, maybe 
> it makes sense to create a MariaDbAdapter (which inherits from Mysql), there 
> is another way to fix that (proposed above)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Closed] (JDO-781) ForeignKey constructor should be called with consistent initiallyDeferred value

[Andy Jefferson (Jira)]

 [ 
https://issues.apache.org/jira/browse/JDO-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy Jefferson closed JDO-781.
--
Resolution: Invalid

Nothing to do with the Apache JDO project

> ForeignKey constructor should be called with consistent initiallyDeferred 
> value
> ---
>
> Key: JDO-781
> URL: https://issues.apache.org/jira/browse/JDO-781
> Project: JDO
>  Issue Type: Improvement
>Reporter: László Bodor
>Priority: Major
>
> https://github.com/datanucleus/datanucleus-rdbms/blob/master/src/main/java/org/datanucleus/store/rdbms/table/TableUtils.java#L131
> {code}
> ForeignKey fk = new ForeignKey(fieldMapping, storeMgr.getDatastoreAdapter(), 
> referencedTable, true);
> {code}
> as we have reference here for the datastore adapter, initiallyDeferred=true 
> parameter could be changed to:
> {code}
> storeMgr.getDatastoreAdapter().supportsOption(DatastoreAdapter.DEFERRED_CONSTRAINTS)
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)