> I'm in the process of writing my first Django project, which has a > calendar application. I'm not quite sure how I should model reccurring > events. My first idea was to use a Event table (containing all the > event data), and a RecurringEvent table which has only two rows: > parent (ForeignKey to an event instance) and date. If the event is a > weekly event, I just insert, say, 52 recurring events and insert more > with a daily cronjob if necessary. Problem is, to the user there > should be no difference in viewing and handling normal events and > recurring events, which is a little hard with this design. Fetching > normal events and recurring events with a single queryset seems not to > be possible, too.
What about having single Event objects that have a m2m with Time objects? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
