How does that help the 1000-record limit? Do you mean get the nearby clubs and just do all the rest manually?
Ian http://examples.roughian.com 2008/11/6 yejun <[EMAIL PROTECTED]> > > In practical, you only need to search a few club geographically close > to each other. So an brutual force scan is the simplest way. > A query cross global seems pretty meaningless beyond statistical > reasons. > > On Nov 6, 8:14 am, "Ian Bambury" <[EMAIL PROTECTED]> wrote: > > 2008/11/6 powera <[EMAIL PROTECTED]> > > > > > > > > > Can't you create an index on a "Bookings" entity based on time, so you > > > can do a query "SELECT * FROM Bookings WHERE time = 1PM" ? If you can > > > keep the list of courts in memcache, it should be easy to compare this > > > list to the list of courts to find open listings at any given time. > > > With an index, you shouldn't have to worry about the 1000-item limit > > > unless you envision having more than 1000 reservations for a given > > > time. > > > > If someone searches for a free bowling lane for tomorrow evening between > 5 > > and 10pm and say the average is 20 lanes per business, then I only need > 10 > > bowling alleys and I'm at the limit > > > > If someone searches for a free lane any evening next week, then 3 bowling > > alleys will break the limit. > > > --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
