I know this discussion has came up before, but I could not find an issue (if there is one) for it. If you create one I'll star it.
Robert On Fri, Oct 22, 2010 at 14:13, leo <leo.ant...@gmail.com> wrote: > Hi, > my understanding is that when you put an entity in the datastore you > decide which properties are indexed and which ones are unindexed so > that instance won´t be found when searching (using single or composite > indexes) by a unindexed property. > > My problem is that I have many queries using a single property with > ancestors, so that mean I have to index the instance and that will > appear in 3 indexes (the two built-in indexes for the property and the > composite index with the property and ancestors). But I´ll be really > be using just one index. > > Is there any way to avoid this, i.e. be able to use properties in > composite indexes without these properties being used in single > property indexes ? > > Is this a limitation on the platform/bigtable or it might change in > the future ? (for instance, allow to disable some single property > indexes in a kind). > > > Thanks. > > -- > 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-appeng...@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. > > -- 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-appeng...@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.
