On Wed, Nov 5, 2008 at 8:20 PM, Ian Bambury <[EMAIL PROTECTED]> wrote:
> But really the question is a more general one of how do you approach this > scenario with an open-ended number of clubs? In a normal relational > database, you could hold just the booked slots and with one SQL request, get > the top 20 available courts by time, distance or whatever. My client is very > keen on using GAE, so I need to find a scalable way of doing it, or a very > solid reason to use a relational DB. SQL databases are great at hiding really horribly-inefficient queries. What "scalable" means is often hard to see on a traditional SQL database, since its "simple" queries are really turning into big table or index scans behind the scenes. It requires a good DBA to keep that scalable. Dave. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
