Fixed in trunk.
On Fri, Jan 8, 2010 at 10:31 AM, Max Ross (Google) <
maxr+appeng...@google.com > wrote:
> Issued filed:
> http://code.google.com/p/datanucleus-appengine/issues/detail?id=185
>
>
> On Fri, Jan 8, 2010 at 10:12 AM, Max Ross (Google) <
> maxr+appeng...@google.com > wrote:
>
>> I'm re
Issued filed:
http://code.google.com/p/datanucleus-appengine/issues/detail?id=185
On Fri, Jan 8, 2010 at 10:12 AM, Max Ross (Google) <
maxr+appeng...@google.com > wrote:
> I'm really sorry but I've been unable to construct an equivalent query that
> avoids this bug. If the size of keyList isn't
I'm really sorry but I've been unable to construct an equivalent query that
avoids this bug. If the size of keyList isn't too large I'd recommend
executing a batch get to retrieve all those objects by id and then applying
the rest of your filter in-memory.
Sorry for the trouble.
Max
On Fri, Jan
Thanks for the report, looks like a bug. Multiple contains() clauses are
fine but I didn't properly account for the case where one of the clauses is
on the primary key of the object. The fix should be straightforward but let
me see if I can get you a workaround.
Max
On Thu, Jan 7, 2010 at 7:06
Basically i have 3 fields in the same table to select by
using .contains() clauses - one is the primary key field
so :keyList (java.util.Set) , :feedTypes (java.util.Set)
& :contentTypes(java.util.Set) with values i need to select
with.
The Feed object (and the relevant fields) is
@PersistenceCap
