For every single parameter there is an index, implicit, with ascending order. If you want a different ordering or combining multiple parameters, and one comparison operator is not the equality you get an entry in index.yaml.
indexed=false prevents the update of the implicit indices. 2009/10/28 Carlos <carlos.p...@gmail.com>: > > Followup question... > > Does "indexed=false" just put a constraint on the data model? In > other words, if there weren't any queries that used this property in > the first place (and thus no index was ever created that included the > property) then adding this parameter doesn't make an immediate > difference? > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
