Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jdo-dev@db.apache.org
Received-SPF: pass (nike.apache.org: local policy)
From: Craig L Russell <craig.russell@oracle.com>
To: jdo-dev@db.apache.org
In-Reply-To: <4D706A8F.8050903@sonic.net>
Subject: Minutes: JDO TCK Conference Call Friday, Mar 4, 9 am Pacific Time
References: <4966C3D9.9050408@sun.com> <4C1AECC6.4060608@son! ic.net>
 <4C241BFB.9060007@soni!    <4C2D64A9.9040908@sonic.net>
 <4C368F03.4050006@son!    <4C405CCC.7030101@sonic.net>
 <4C52CB42.7070009@soni!    <4C5B7B21.7090304@so! <4C64AFFE.9070403@son!
    <4C6DFFB4.3030802@sonic.net> <4C7738AE.8020405@soni!
    <4C805FB2.8040400@so! <4C89A9C0.8070500@son!
    <4C92CEA0.1080904@sonic.net> <4C9C1C82.4090007@soni!
    <4CA5597A.30801@sonic.net>
 <79f3420acc7d5b2c4cb90280a4ee555d.squirrel@webmail.sonic.net>
 <4CB7CAF0.2020904@sonic.net> <4CC10840.1060208@so! nic.net>
 <4CCA3F7F.9080501@sonic.net> <4CD41396.1070000@sonic.n! et>
 <4CDCA65B.7040303@sonic! .net> <4CE5DEB4.8070501@sonic.! net>
 <4CEF29A0.8020102@soni! c.net> <4CF86D72.1010509@sonic! .net>
 <4D019857.5010504@son! ic.net> <4D0AD51B.5040700@soni! c.net>
 <4D26919C.7060100@so! nic.net> <4D2FC2BB.8080402@son! ic.net>
 <4D38FBC0.9060109@sonic.net> <4D4234D8.50102@sonic.ne! t>
 <4D4B6ABE.5090700@sonic.ne! t> <4D672BBB.4030607@sonic.net!
 > <4D706A8F.8050903@sonic.net>
Message-Id: <A64F3D5E-09DC-462C-B9D5-53470BEF78B1@oracle.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Fri, 4 Mar 2011 10:02:39 -0800
Cc: JDO Expert Group <jdo-experts-ext@sun.com>

Attendees: Michelle Caisse, Michael Bouschen, Craig Russell

Agenda:

1. Maven 2 upgrade - using setting.xml or profiles.xml for iut profile https://issues.apache.org/jira/browse/JDO-647

Apparently maven doesn't want to encourage items in the settings.xml  
to affect the build, but we do. Specifically, we want to have the  
user's settings.xml to provide settings to run the iut. Any suggestions?

2. Typesafe ... query capability for JDOQL - ready for check-in?. https://issues.apache.org/jira/browse/JDO-652

Some questions: the factory for query instances: should it be PM or  
PMF? Hint: do you really need to have the PM available in order to  
build a query? The PM represents your current connection to the  
database; the PMF represents the object model and mapping.

Also, the name sounds too "inside". Matthew made a similar comment.  
I'd like to look at the name: "TypesafeQuery".

Is there a bug in the blog?
List<Object[]> results =  
em.createQuery(criteria).getSingleResult(); // should return Object[]?
List<Integer> result =
tq.filter(cand.name.eq("MP3  
Extra")).executeResultUnique(Integer.class, cand.value.max()); //  
should return Integer?
Method name for returning projection might not be obvious.

Started looking at it in detail with an eye to including in 3.1. Not  
done yet.

3. Ability to mark a class as read-only - https://issues.apache.org/jira/browse/JDO-677

Seems like a good idea. Anyone else have comments?

Where would an error be identified? At the time the user modifies a  
persistent field? Or defer checking until flush (or commit)?

Portable behavior would probably mean defer checking.

Silently ignoring an update is probably not the right behavior.

4. Other issues

JDO-678 Set properties on PersistenceManager

Seems like a good idea. Patch?

Action Items from weeks past:
[Feb 25 2011] AI Michael, Craig, other volunteers: Look at  
Typesafe ... query capability for JDOQL https://issues.apache.org/jira/browse/JDO-652

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!