I've just started using Django (and I'm very impressed), but I'm not sure of the "official" way to handle updates for my latest application, which records a timetable of regular visits by a person to somewhere. The structure (somewhat simplified) is :
A VISIT has a start time and and end time (but no date). A SCHEDULE describes what happens over the course of a single day, and has one or more visits which will take place on the same day. It also has one or more days of the week to which it applies (all the days which have the same pattern of visits). A PLAN describes all the schedules in use for a week, and has one or more schedules. Example: PLAN for Joe has 2 Schedules. SCHEDULE A - applies to Mon/Wed/Fri and has 2 visits. VISIT A1 - start 10am end 11am VISIT A2 - start 2pm end 4pm SCHEDULE B - applies to Tue/Thu and has 3 visits. VISIT B1 - start 10am end 11am VISIT B2 - start 3pm end 4pm VISIT B3 - start 5pm end 6pm Although visits A1 and B1 are at identical times, they are separate entities in the database. Schedule:Plan is one:many and Plan:Visit is one:many. I envisage one web form to enter a new Plan, or update some part of an existing one. Obviously I can "roll my own", but is there a preferred django way? Generic views don't seem to do it. I had a look at custom manipulators, and I wasn't quite clear whether I can use them there or not. Or should I change my database (model) design? Thanks --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
