Certain queries are satisfiable using built-in indexes - any number of equality filters (without order or inequality filters), entity and ancestor queries, and inequality or ascending sort order queries on a single property. These queries are all indexed - they just don't require custom indexes.
-Nick On Tue, Apr 14, 2009 at 8:06 PM, PJ Fitzpatrick < [email protected]> wrote: > When i go to the Admin console and select Indexes i get > > You have not created indexes for this application. > > In the index.yaml file i uploaded there are no indixes. > > tks, > PJ > > > > > On Tue, Apr 14, 2009 at 7:45 PM, Nick Johnson <[email protected]> wrote: > >> Unindexed queries? That's not possible in production App Engine. What do >> you mean? >> >> -Nick >> >> >> On Tue, Apr 14, 2009 at 6:55 PM, PJ Fitzpatrick < >> [email protected]> wrote: >> >>> Hi, >>> As I mentioned last week in my talk last week i planned to do some tests >>> on my exchange application in a live environment. I tested two of the key >>> transaction types input of an item and an order on an item. They worked very >>> well. The times were as low as 357ms and averaged somewhere around a second. >>> I was especially happy with the order input as it requires queries (which >>> are unindexed at the moment as i cannot figure how to get them >>> autogenerated) and does a lot of datastore writes within a transaction. >>> tks, >>> PJ >>> >>> >>> >>> >>> >>> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Python Ireland" 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.ie/group/pythonireland?hl=en -~----------~----~----~----~------~----~------~--~---
