Does the NDB membership query (“IN” operation) performance degrade with lots of possible values?
问题 The documentation for the IN query operation states that those queries are implemented as a big OR'ed equality query: qry = Article.query(Article.tags.IN(['python', 'ruby', 'php'])) is equivalent to: qry = Article.query(ndb.OR(Article.tags == 'python', Article.tags == 'ruby', Article.tags == 'php')) I am currently modelling some entities for a GAE project and plan on using these membership queries with a lot of possible values: qry = Player.query(Player.facebook_id.IN(list_of_facebook_ids))