The suggestion looks good. thanks.
On Thu, Jan 19, 2017 at 1:00 AM, Jason Collins
wrote:
> Add a new field called, e.g, queryableStatus that is a list of strings.
> Then pre-compute your query logic so that you only need an equality filter.
>
> E.g, when saving the entity (warning: pseudocode
Add a new field called, e.g, queryableStatus that is a list of strings.
Then pre-compute your query logic so that you only need an equality filter.
E.g, when saving the entity (warning: pseudocode ahead):
if status in ['PAID', 'PARTIALLY_PAID']:
invoice.queryableStatus.append('PAID_OR_PART
Good thing I didn't rewrite my code before asking :-).
I see the asynctools Jason posted, but I would be looking for a join
(in the thread sense) that allows continued processing once all the
results are back.
On Fri, Sep 4, 2009 at 8:44 AM, Nick Johnson
(Google) wrote:
> Hi Jeff,
> IN queries ar
In the meantime, you can use http://code.google.com/p/asynctools/ to
kick off parallel queries.
It doesn't (yet) directly support MultiQuery, so you'll need to
rewrite your IN queries as a set of equality queries.
j
On Sep 4, 9:44 am, "Nick Johnson (Google)"
wrote:
> Hi Jeff,
> IN queries are
Hi Jeff,
IN queries are split up into multiple basic queries entirely in user code,
so there's no latency or other benefit to using them over doing multiple
queries yourself - it's just for convenience. In future, though, the
MultiQuery interface may be extended to do its queries in parallel.
-Nic
