Ian Bambury 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.
Is a billion records that bad for 10,000 clubs with 10 courts each? Really, at that scale, you have a true enterprise application, and the storage for a billion records is likely to just be a few hundred gigabytes. Fits on one hard disk. If you really don't want to store too far in advance, then you can use a separate entry for the club/date combination, and only pre-allocate records for a club/date combination when someone wants to book (and then mark that club/date as not fully available). The nice side effect of that would be that certain clubs can shut down for certain dates (christmas, international hello day, or whatever). Thus, you'd select a court either if the booking time is empty, or if the club/date for the desired date says "everything is free." However, that sounds like a complication you should put off until it's shown that you actually need it. Sincerely, jw --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
