StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>There's no single answer to this question. The datastore is really low level and it's up to you to create the right indexes and preprocess data so it can be retrieved faster. Also, depending on concurrent access to the same entity, you'd have to use pretty creative stuff like <a href="http://code.google.com/appengine/articles/sharding_counters.html" rel="nofollow">http://code.google.com/appengine/articles/sharding_counters.html</a></p> <p>I can recommend you watching two Google I/O Sessions to get you started <a href="http://sites.google.com/site/io/under-the-covers-of-the-google-app-engine-datastore" rel="nofollow">http://sites.google.com/site/io/under-the-covers-of-the-google-app-engine-datastore</a> gives you a low-level overview of how everything works and why they were done this way (down to how the sectors are written to disk)</p> <p>Then <a href="http://sites.google.com/site/io/building-scalable-web-applications-with-google-app-engine" rel="nofollow">http://sites.google.com/site/io/building-scalable-web-applications-with-google-app-engine</a> will show you how to use that low level stuff in real world applications. </p> <p>There's another one which presents other solutions to common problems <a href="http://www.google.com/events/io/2009/sessions/BuildingScalableComplexApps.html" rel="nofollow">http://www.google.com/events/io/2009/sessions/BuildingScalableComplexApps.html</a> - nice to open your mind to new kinds of solutions to the datastore's limitations.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload