Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Here is a good link: One to Many Join using Google App Engine.</p> <p><a href="http://blog.arbingersys.com/2008/04/google-app-engine-one-to-many-join.html" rel="nofollow noreferrer">http://blog.arbingersys.com/2008/04/google-app-engine-one-to-many-join.html</a></p> <p>Here is another good link: Many to Many Join using Google App Engine:</p> <p><a href="http://blog.arbingersys.com/2008/04/google-app-engine-many-to-many-join.html" rel="nofollow noreferrer">http://blog.arbingersys.com/2008/04/google-app-engine-many-to-many-join.html</a></p> <p>Here is a good discussion regarding the above two links:</p> <p><a href="http://groups.google.com/group/google-appengine/browse_thread/thread/e9464ceb131c726f/6aeae1e390038592?pli=1" rel="nofollow noreferrer">http://groups.google.com/group/google-appengine/browse_thread/thread/e9464ceb131c726f/6aeae1e390038592?pli=1</a></p> <p>Personally I find this comment in the discussion very informative about the Google App Engine Data Store:</p> <p><a href="http://groups.google.com/group/google-appengine/msg/ee3bd373bd31e2c7" rel="nofollow noreferrer">http://groups.google.com/group/google-appengine/msg/ee3bd373bd31e2c7</a></p> <blockquote> <p>At scale you wind up doing a bunch of things that seem wrong, but that are required by the numbers we are running. Go watch the EBay talks. Or read the posts about how many database instances FaceBook is running.</p> <p>The simple truth is, what we learned about in uni was great for the business automation apps of small to medium enterprise applications, where the load was predictable, and there was money enough to buy the server required to handle the load of 50 people doing data entry into an accounts or business planning and control app....</p> </blockquote> <p>Searched around a bit more and came across this Google Doc Article:</p> <p><a href="http://code.google.com/appengine/articles/modeling.html" rel="nofollow noreferrer">http://code.google.com/appengine/articles/modeling.html</a></p> <blockquote> <p>App Engine allows the creation of easy to use relationships between datastore entities which can represent real-world things and ideas. Use ReferenceProperty when you need to associate an arbitrary number of repeated types of information with a single entity. Use key-lists when you need to allow lots of different objects to share other instances between each other. You will find that these two approaches will provide you with most of what you need to create the model behind great applications.</p> </blockquote>
 

Querying!

 
Guidance

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