We upgraded to appengine-java-sdk 1.2.5 today (from 1.2.2) and the
performance seems to
be back to what we were experiencing earlier which was well under a
second for 100 entities.
We're not sure why but the performance when we were using 1.2.2 was
similar to not specifying
the one to one owned f
If you know what these names and countries are in advance, you can do a
write-time check and mark each entity when it's persisted, so you only have
to query on a single boolean field, for example. Even if the list of names
and countries can change over time, you can write a script to re-process all
Thanks for the replies.
Both listA and listB may contain tens of elements, so the combination
may be 10 to 1000.
I am not sure what you mean by "Are the values in listA and listB
stored". As in my example, I am querying against property name, and
its value is surely stored.
Awaiting...
Thanks,
Ra
I agree with Iain: it depends on how many items are in the lists. But
for large lists, I don't think it would work out very well.
Are the values in listA and listB stored? That might give you more
options.
On Aug 20, 8:15 pm, Ray Li wrote:
> Hi,
>
> I have a query filter on an entity Person t
Option 1 sounds fine. That is how python implements a WHERE a IN
(1...n). It will execute up to 30 queries. How many do you expect?
And how many results do you expect for each individual query?
On Aug 21, 11:15 am, Ray Li wrote:
> Hi,
>
> I have a query filter on an entity Person that person.na
