Something I truly do not understand, is why so many people persist in talking about tables (and all that "tables" implies) when when designing applications using the datastore especially with so much documentation available covering what the datastore does and how it works. The datastore has been around since 2008, (and similiar datastores since 2000 and even earlier) this isn't new stuff.
It's just not a relational model and there is no SQL. If people don't sit back and try and understand how it works and what features it does have, they can't exploit its model and will invariably make bad design decisions. Is this because no one reads/understands documentation anbd won't explore, or is a particular mindset so ingrained that any other way becomes difficult ? T On Sunday, April 6, 2014 10:46:04 PM UTC+8, Julien De Almeida wrote: > > Hello, > > I want to create a Map object with key a Party and value a Player. > But I don't know how to "join" this two entity. > My entity "Party" have three fields (id, player1_id and player2_id). > My entity "Player" have three fiedls (id, email and surname) > > I want to join like that : > "SELECT * FROM Party, Player WHERE Party.player1_id = Player.id AND > Party.player2_id IS NULL;" > > Someone can help me? > > Thx > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
