That's challenging. If there's a finite set of possible property names, you
can generate all these ahead of time using queries on your local datastore
instance. If not, you may want to reconsider using the property name as
metadata for exactly the reasons you mentioned. For properties that require
I use the low level App Engine data store API, as it gives me the
flexibility of having defining schemas on the fly, as Entities on the
app engine don't really need a schema.
Normally, if i needed to define a composite index that is based on an
Entity's property and its ancestor; i can do so by de
