This was previously mentioned (no resolution/answer) in http://groups.google.com/group/google-appengine/browse_thread/thread/1285c272c0e1b62a
On Mar 3, 7:36 pm, Devel63 <[email protected]> wrote: > I just implemented something like this, and while it ran fine on the > dev_server, I noticed that it defined in index.yaml a new index for > every observed number of items in the IN set. > > Since I was approaching the 30 limit, and had other varying elements > of the query, this caused an explosion of defined indexes. But > perhaps these indexes aren't really needed... > > Have either of you tried running an IN query on the production server > WITHOUT this explosion of indexes? > > On Mar 3, 2:36 pm, ryan <[email protected]> wrote: > > > > > On Mar 3, 12:26 pm, pedepy <[email protected]> wrote: > > > > isnt the proper syntax WHERE property IN (foo, foo, foo) ? > > > if you're providing a list of constants, yes. if you're using a bound > > parameter, though, like in your original post, you should omit the > > parentheses. > > > having said that, it looks like we may sometimes handle list bound > > parameters incorrectly, particularly with parentheses around them. > > i'll look into that. thanks for the report!- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
