« Return to Thread: Subquery specification update

Re: Subquery specification update

by Matthew T. Adams-2 :: Rate this Message:

Reply to Author | View in Thread

I agree that the candidateCollectionExpression description is a bit  
cryptic.

Boy, it's been a long time since I thought about subqueries.  Can we  
also provide single-string versions of the examples?  That would be  
helpful.

-matthew

On Oct 25, 2007, at 5:07 AM, Christiaan wrote:

>
> Hi Craig,
> the examples are very informative. I must say that I find the  
> description
> for candidateCollectionExpression
> "The candidateCollectionExpression is the expression using tokens from
> this query that represent the candidates over which the subquery is
> evaluated. "
> a little bit cryptic (I actually find the paramater name more  
> descriptive
> than the description). Especially "tokens from this query" (is  
> tokens a
> common word for this and may be it should be stressed that this  
> query is the
> outer query?) and "over which the subquery is evaluated", but may  
> be this is
> needed for the spec.
>
> Anyway, do I understand it correctly that it is the same as:
> ....
> sub.setFilter(":departmentEmployees.contains(this)");
> Query q = pm.newQuery(Employee.class);
> q.setFilter("this.weeklyHours > averageWeeklyhours");
> q.addSubquery(sub, "double averageWeeklyhours",  null,
> "this.department.employees");
>
> kind regards,
> Christiaan
> --
> View this message in context: http://www.nabble.com/Subquery- 
> specification-update-tf4686785.html#a13405438
> Sent from the JDO - Development mailing list archive at Nabble.com.
>

 « Return to Thread: Subquery specification update