you could also created derivative entity which combined both country and state and query for it == operator.
On Sat, Sep 10, 2011 at 11:32 AM, Thomas Wiradikusuma < [email protected]> wrote: > Hi guys, > > I have this entity: > > House { > - country > - state > - address > - owner > - ... > } > > Since I will *always* limit queries to be inside specific country > +state combo, would it be more efficient (faster, smaller datastore, > smaller index) if I just shard them into different entities? E.g.: > > HouseBaId (for houses in Bali, Indonesia), HouseTxUs (for houses in > Texas, US), etc. > > Query-wise, it is shorter, e.g. "select * from HouseUsTx" instead > "select * from House where country = 'us' and state = 'tx". > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
