On 3/8/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: ... > Also I store these Schedules as a top level table. I then create > Resources (Events?) that "use" a specific schedule. This way I can > have lots of Resources that use the same Schedule, again minimising > the number of schedule records.
It seems we all have this problem. :) I was thinking about doing something similar to what Gary's doing, but I'm more concerned with fast access than minimal records. Also, there's a "reasonable" window of time for which we'll ever have records, say 10 years. As such, I was thinking about having an Event model with recurrence rules (perhaps admin'd with a little DSL), then blowing out a lot of EventTime records for all the occurrences. Editing would always be to Events; EventTimes would be regenerated upon Event save. The reduces queries to a simple date range, allowing very efficient index usage. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
