Thanks Andy, Ian http://examples.roughian.com
2008/11/6 Andy Freeman <[EMAIL PROTECTED]> > > On Nov 6, 7:48 am, "Ian Bambury" <[EMAIL PROTECTED]> wrote: > > Well, that is good news. If the index is in date-time order, how does it > > avoid having to scan the index for the status of the 'booked' flag? If > the > > index is in 'booked' flag order, how does it avoid having to scan for > > date-time? > > GAE uses the same trick that SQL databases have been using for years > to avoid a table scan in that situation, namely an index that includes > both date-time and booked information. > > Responsive SQL applications don't scan large tables. GAE applications > should be designed the same way. > > GAE provides a significant amount of help in determining the > appropriate indices. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
