google-cloud-datastore

How do I get the equivalent result of the following query in NDB? Entity.all(keys_only=True).fetch(20) I know you can pass 'keys_only=True' to the iter() method. But what if I want to perform a keys only fetch, how do I do that in NDB? Found it in the GAE NDB Docs . The answer is Entity.query().fetch(20,keys_only=True) . 来源： https://stackoverflow.com/questions/10203874/whats-the-equivalent-of-entity-allkeys-only-true-fetch20-in-ndb

Is there a way to use a real database(SQLite, Mysql, or even some non-relational one) as datastore for development, instead of memory/file datastore that is provided. I saw few projects, GAE-SQLite(did not seem to be working) and one tip about accessing production datastore using remote api (still pretty slow for large datasets). MongoDB works great for that. You will need: The MongoDB stub: http://github.com/mongodb/mongo-appengine-connector MongoDB: http://www.mongodb.org/display/DOCS/Downloads Some code to set it up like: code: import datastore_mongo_stub os.environ['APPLICATION_ID'] =

I have read several similar questions on StackOverflow but haven't found a solution to this problem yet. I am uploading a blob from Android to App Engine's Blobstore through an HTTPPost to the upload URL generated by the Blobstore service. I want to be able to send some textual metadata with this request that identifies this blob. I want to retrieve this information along with the blob key in the upload handler servlet that is called after the blob is uploaded. The problem is that the blob is uploaded using multipart encoding and App Engine does not support the Servlet v3.0 standard, so I can

I'm a total App Engine newbie, and I want to confirm my understanding of the high replication datastore. The documentation says that entity groups are a "unit of consistency", and that all data is eventually consistent. Along the same lines, it also says "queries across entity groups can be stale". Can someone provide some examples where queries can be "stale"? Is it saying I could potentially save an entity without any parent (ie. it's own group), then query for it very soon after and not find it? Does it also imply that if I want data to be always 100% up-to-date I need to save them all in

How to reset quota if Datastore Write Operations limit is reached ? Any operation (both from admin console and from my code) on datastore reports the following error: The API call datastore_v3.Put() required more quota than is available. I have tried to disable application and wait for quota reset, but it did not work. When the app is enabled, it produces a lot of tasks that in turn try to operate on datastore, what obviously consumes the quota. Now, I have paused the task queues and will give another try waiting 24 hours. Is it the right solution ? aschmid00 The quota is reset every 24h, so

Suppose I have class Foo(db.Model): bar = db.ReferenceProperty(Bar) foo = Foo.all().get() Is there a way for me to do foo.bar without a query being made to Datastore? The docs say that foo.bar will be an instance of Key , so I would expect to be able to do foo.bar.id() and be able to get the id of the Bar that's associated with foo , but it doesn't seem to work that way. PS: The part of the docs I'm referring to can be found here: http://code.google.com/appengine/docs/python/datastore/typesandpropertyclasses.html#ReferenceProperty and it says this: "An application can explicitly db.get() the

The Google App Engine Datastore querying language (gql) does not offer inexact operators like "LIKE" or even case insensitivity. One can get around the case sensitive issue by storing a lower-case version of a field. But what if I want to search for a person but I'm not sure of the spelling of the name? Is there an accepted pattern for dealing with this scenario? Quoting from the documentation: Tip: Query filters do not have an explicit way to match just part of a string value, but you can fake a prefix match using inequality filters: db.GqlQuery("SELECT * FROM MyModel WHERE prop >= :1 AND

I'm trying to better understand the implications of the deep hierarchy described in the GAE NDB docs "For example, a revision of a message that "belongs to" an owner, might have a key that looks like" rev_key = ndb.Key('Account', 'Sandy', 'Message', 'greeting', 'Revision', '2') I interpret this to mean that if I do Revision(parent=rev_key).put() then I will have an entity group at the Revision=2 level meaning ancestor queries where ancestor=rev_key will have strong consistency and writes where parent=rev_key will be limited to 1/sec. But what are the implications further up the hierarchy? For