Hi Kyle,
Exploding indexes only come into play when you're _defining_ indexes - for
example, an index like this would be an exploding one:
- kind: Foo
property: tags
property: tags
As long as you can satisfy your queries using the built in merge join
support (which is the case in your example, where you don't specify
inequality filters or sort orders), you'll be fine.
-Nick Johnson
On Mon, Jul 27, 2009 at 3:50 PM, Kyle Jensen <kljen...@gmail.com> wrote:
>
>
> Hi, I'd like to know if multiple equality filters on a ListProperty
> leads to exploding indexes.
>
> I have a model something like the following (python):
>
> class Foo(db.model):
> tags = db.ListProperty(db.Category)
>
> @classmethod
> def get_by_tags(cls, tags):
> query = cls.all()
> for tag in tags:
> query.filter('tags =', tag)
> return query
>
> I'd like to know if I can filter by an arbitrary number of tags
> without encountering the exploding index problem (its not clear to me
> from the docs).
>
> E.g., can I do
> query = Foo.get_by_tags(['tag0', 'tag1', 'tag2', 'tag3' .... 'tagN'])
>
> etc etc.
>
> Thanks! Kyle
> >
>
--
Nick Johnson, Developer Programs Engineer, App Engine
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
