google-cloud-datastore

问题 I want to know how to evaluate one tool over another. My major concern is as following: In google datastore, we define 'kind'. Each 'entities' has 'properties'. Then the datastore backends use those properties to index data for future query. The query itself use almost the same idea in SQL, though different syntax, to filter data and find what we want. If you index every property, the index metadata would be even bigger than real data. Google bigquery uses it's dialect of SQL. And it's fully

问题 Can we start a dynamic backend programatically? mean while when a backend is starting how can i handle the request by falling back on the application(i mean app.appspot.com). When i stop a backend manually in admin console, and send a request to it, its not starting "dynamically" 回答1: Dynamic backends come into existence when they receive a request, and are turned down when idle; they are ideal for work that is intermittent or driven by user activity. Resident backends run continuously,

问题 I know you are supposed to add @Index to all properties in your entity model to add an index, but what if you forget and there are already live writes of your entity in the datastore? Is there a way to manually add an index to all those properties via the developers console or some other way? I found that if you add @Index to your entity and re-deploy the project, all new writes of that entity will have that property indexed. However, all existing writes of that property will not be indexed

问题 I know you are supposed to add @Index to all properties in your entity model to add an index, but what if you forget and there are already live writes of your entity in the datastore? Is there a way to manually add an index to all those properties via the developers console or some other way? I found that if you add @Index to your entity and re-deploy the project, all new writes of that entity will have that property indexed. However, all existing writes of that property will not be indexed

问题 As a Python programmer, I like my code to be reusable, I'm trying to avoid kind name conflicts in my code (where two different models share the same kind name). Currently I just prepend some meaningful text to the model's class name, but this is awfully unpythonic. Being able to explicitly set the model's kind will solve my problem, but I can't find out how to do this, does anyone know how? 回答1: Just override the kind() method of your class: class MyModel(db.Model): @classmethod def kind(cls)

问题 I'm trying to upload multiple files in a form to the BlobStore. Form: <form action="{{upload_url}}" method="POST" enctype="multipart/form-data"> <label>Key Name</label><input type="text" name="key_name" size="50"><br/> <label>name</label><input type="text" name="name" size="50"><br/> <label>image</label><input type="file" name="image" size="50"><br/> <label>thumb</label><input type="file" name="thumb" size="50"><br/> <input type="submit" name="submit" value="Submit"> </form> I'm then trying

问题 I'm trying to upload multiple files in a form to the BlobStore. Form: <form action="{{upload_url}}" method="POST" enctype="multipart/form-data"> <label>Key Name</label><input type="text" name="key_name" size="50"><br/> <label>name</label><input type="text" name="name" size="50"><br/> <label>image</label><input type="file" name="image" size="50"><br/> <label>thumb</label><input type="file" name="thumb" size="50"><br/> <input type="submit" name="submit" value="Submit"> </form> I'm then trying

问题 Following up on my earlier question regarding GAE Datastore entity hierarchies, I'm still confused about when to use entity groups . Take this simple example: Every Company has one or more Employee entities An Employee cannot be moved to another Company , and users that deal with one Company can never see the Employee s of another Company This looks like a case where I could make Employee a child entity of Company , but what are the practical consequences? Does this improve scalability, hurt

问题 Currently I am working on new App Engine application. Unfortunately it seems that my application uses to lot of resources even for relatively small user number. So I need to determine its bottle necks and optimize them. 回答1: Appstats: RPC Instrumentation for Google App Engine. It is being developed by Guido himself. alt text http://img130.imageshack.us/img130/526/timelinea.png EDIT : I believe AppStats will not work with Java, but there are some tips here. 回答2: The Eclipse plugin for the

问题 Currently I am working on new App Engine application. Unfortunately it seems that my application uses to lot of resources even for relatively small user number. So I need to determine its bottle necks and optimize them. 回答1: Appstats: RPC Instrumentation for Google App Engine. It is being developed by Guido himself. alt text http://img130.imageshack.us/img130/526/timelinea.png EDIT : I believe AppStats will not work with Java, but there are some tips here. 回答2: The Eclipse plugin for the