db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Craig L Russell <Craig.Russ...@Sun.COM>
Subject Re: JDO TCK Conference Call Friday, Dec 7 , 9 am PST
Date Fri, 07 Dec 2007 17:46:57 GMT
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell

Agenda:

1. Serializing PersistenceManager. AI Craig update the spec and send  
around for review.

2. Other issues

Delete consistency. AI everyone review and comment.

Query subquery. Might need some more assertions. AI review the  
subquery section.

Query update: Why is it called perform instead of update? Just to  
reinforce the idea that you select a number of Java instances and  
perform some block action on them. But there's nothing wrong with  
calling it update. Question: should we put additional restrictions on  
the perform block to map 1-1 with SQL? Perhaps not. In particular,  
should it be permitted to use variables to update related instances?  
Even if we restrict the operations to only the candidate class,  
multiple SQL statements or subqueries might be needed for inheritance  
and existential queries. AI Michael reply to email thread.

It looks like the last major issue is serialization of instances for  
the life cycle tests. There are still several instances of  
UNSPECIFIED in the tests, and these will be reviewed to see which  
should be specified for 2.1. Also, CopyOnAttach flag is currently  
true in all the tests. There also need to be tests for CopyOnAttach  
false.

Action Items from weeks past:

[Nov 30 2007] AI Craig update the spec with some assertions for  
subqueries. AI Michael implement  the test cases https:// 
issues.apache.org/jira/browse/JDO-446

[Nov 30 2007] AI Christiaan propose more details on Update/copy by  
query for post-JDO 2.1.

[May 25 2007]  AI everyone download the Grails demo from grails.org   
and check it out. Also look at Grails/Groovy ExpandoMetaClass that   
has the magic to avoid reflection and enhancement.

[May 25 2007] AI Matthew Adams prepare a proposal with just the  
basics of schema synchronization with jdo and orm metadata.

[Mar 9 2007] AI Craig: Update the spec to require that the key of the  
listener is the class name of the listener, for consistency with   
proposed xml.. .

[Aug 11 2006] AI Craig propose some semantics for behavior if user  
tries to add to a list where the ordering element is incorrect.

[Sep 2 2005] AI: To recruit members:  Articles on  TheServerSide  
directing attention to the site. T-shirts.  AI:   Craig write a  
ServerSide article.

-- Michelle

Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!


Mime
View raw message