hi, guys: Is there any update on this issue? I am running into the same problem when I query on candidates: I used the empty list returned from first query as the candidates of the second query, however result of the second query is not empty.
On Nov 4, 10:08 pm, datanucleus <[email protected]> wrote: > > App Engine's DataNucleus plugin doesn't support the setCandidates method > > Jason/Max, DataNucleus can do all of that for you, I'm sure I've > mentioned this before. > Here I'll even donate you some code that you can plug into your > JDOQLQuery.performExecute() method > > <code> > if (candidateCollection != null) > { > // Supplied collection of instances, so evaluate in-memory > if (candidateCollection.isEmpty()) > { > return Collections.EMPTY_LIST; > } > else > { > ClassLoaderResolver clr = om.getClassLoaderResolver(); > List candidates = new ArrayList(candidateCollection); > JavaQueryEvaluator resultMapper = new JDOQLEvaluator > (this, candidates, compilation, > parameters, clr); > return resultMapper.execute(true, true, true, true, > true); > } > } > </code> > > So the query will be executed in memory using the user-supplied > instances. > > No excuses now ;-) > > --Andy (DataNucleus) -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
