For example? I am sure there is space for optimizing the list views.. The only trick I know is to reduce the number of order-able columns in the list view...
For example, just yesterday I developed a statistics module which required me to add another 2 indexes for 2 queries like: select * from Customers where accountId = 'currentAccountId' and creationDate > [from] and creationDate < [toDate] and status = 'available' Is there a trick to avoid using indexes on queries like that? Il giorno venerdì 23 marzo 2012 12:28:47 UTC+1, de Witte ha scritto: > > Try > http://support.google.com/code/bin/request.py?contact_type=AppEngineQuotaRequest<http://support.google.com/code/bin/request.py?contact_type=AppEngineQuotaRequest> > > > 200 indexes for 50 entities is a lot and makes your application expensive. > > There are tricks to sort a ListView without using an index for each column. > > > > Op woensdag 21 maart 2012 08:47:06 UTC+1 schreef prakhil samar het > volgende: >> >> Hi >> >> I have a application and my datastore indexes are full i have created >> 200 indexes. >> >> is there any way that indexes can be increased ? >> >> Can i increase indexes by enabling billing on my application ? >> > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/mSg2Pcz8pzIJ. 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.
