9 PM UTC+2, Janne Savukoski wrote:
>
> Hi Jordan!
>
> Thanks for the reply. However, I didn't quite catch how the answer is
> related to my question. But, maybe I can clarify the question with this
> quote: “To be eligible as a query result, an entity must possess a value
>
Hi Jordan!
Thanks for the reply. However, I didn't quite catch how the answer is
related to my question. But, maybe I can clarify the question with this
quote: “To be eligible as a query result, an entity must possess a value
(possibly null) for every property named in the query's filters and s
Hi,
I couldn't find an earlier question about this, so could someone explain
why: “Querying for a value of None on a repeated property has undefined
behavior; don't do that.”[0]
This sounds very weird. Is this some curiosity with the datastore itself,
or just some complication within the NDB l
Hi Rajesh,
I'd suggest to consider moving some queries over to Search API
(https://cloud.google.com/appengine/docs/java/search/). For example, we use
the custom datastore indexes (indices) primarily only for queries which
have strong consistency requirements.
After we adopted this approach of
Heyo,
Are there any differences between Master/Slave and High Replication
regarding transactions? Are the transaction limits the same? (Is the
limit still 4/sec/group or so?) Can I expect any differences in the
rate of TransactionFailedErrors?
I thought of asking this before relying on testing on
Howdy,
Couple versions stuck, can't delete. One in each app: netcycler and
netcycler-qa; I'd rather not publish version names here.
Help?
-Janne
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to google-
ordering is at least
preserved.) Although, to implement this we'd need to maintain a
frequency index ourselves and consulting it slows query building.
And a very long shot: any hunches about any upcoming search service?
Also all other tips are much appreciated!
regards,
Janne Savukosk
Hello,
We're having some problems with emails being sent multiple times. The
core issue is that emails are being sent even if send_mail raises an
error (DeadlineExceededError). (Same issue mentioned in
http://groups.google.com/group/google-appengine/browse_thread/thread/189eecd6021b1bb4/ed1025f01b
I managed to burn the whole taskqueue quota (1M) with some runaway
recursive tasks for one of our apps. My bad, but is there any chance
to get a temporary increase on the quota? Next reset is still 18h
away. :)
appid netcycler-qa
--
You received this message because you are subscribed to the Goo
