Thanks! :)
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/_7jQ8A4UuWcJ.
To post to this group, send email to google-appengine@googlegroups.com.
To
Ikai, let confirm you hypothesis ;) I faced the same problem with parameter
having "new" prefix - renaming the parameter fixed the problem. My code
before fix:
Query
query=pm.newQuery(GaeQuestionAnswerBean.class);
query.setFilter("growKey == newGrowKey && ownerId == userI
Hi all!
I'm looking for a lesson from 'pricing oriented programming'. My service
has a REST-style endpoint that I use to replicate/export/import data.
Surprisingly export consumes ~10x more Datastore Small Operations than
Datastore Read Operations. Thus I'm almost running out of free quota. Ther
Obviously I use memcache through the application. Unfortunately this is not
solution to my problem as the export I described above is typically used
for backup before upgrades and majority of entities is read occasionally.
It may be that I'm wrong. Is it a best practice to have a custom write
t
Obviously I use memcache through the application. Unfortunately this is not
solution to my problem as the export I described above is typically used
for backup before upgrades and majority of entities is read occasionally.
It may be that I'm wrong. Is it a best practice to have a custom write
t
Thanks, I have read this post before I sent my question to the group.
However it 1 count() operation is much more "cheaper" that loading one
entity (that in the collection I checked takes ~7 Datastore Key Fetch Ops on
average).
Actually I need to reformulate the question I originally asked:
I switched my application from 'Google Accounts API' authentication to
'Federated Login'. My application has a REST-style interface and therefore
I need to authenticate programmatically.
It seems that it's not that easy:
http://blog.notdot.net/2010/06/Using-remote-api-with-OpenID-authenticati
