You can have multiple "indexes" on the many side. Decouple the ListProperty
in its own model and use a key only query to find the ancestor key. Then a
db.get will get you what you want.
Example:
class Dude(db.Model):
name = db.StringProperty()
class DudeIndex(db.Model):
relates_to = db.Strin
All,
I am building an application where I need to model a 1-many
relationship. The "many" side of the relationship needs to scale to
about 1 million items at maximum. In his talk, Building Scalable and
Complex Apps, Brett Slatkin suggests using ListProperty to model this
type of relationship; howe
