Hi,
I'm building an app for scheduling conferences and am having a hard time finding a way to make it convenient for the scheduling administrator. Sessions need to be scheduled into time slots and it seems difficult to take advantage of the usual constraints to make scheduling work well. Here are a few issues I am bumping into. * Typically (but not always) every day of a conference has the same set of time slots, so it would be very convenient if the admin interface had a "duplicate this object" function, but I can't find one. * A conference typically runs somewhere between 3 and 6 days, but AFAICT there's no easy way to create a DateField whose choices are limited to days during the conference in the admin interface. As I think about how to build this thing, admin convenience drives me toward a ridiculously granular set of models, e.g. TimeDiv - containing just a time field TimeSpan - containing a pair of timedivs Day - containing just a date field Slot - a timespan and a day but that's surely bad for performance and query convenience. Any insight into how to resolve these tensions? TIA, -- Dave Abrahams Boost Consulting www.boost-consulting.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
