As soon as you need additional reservation-related behaviour (is this timeslot still available?, etc.), this will break the OP's requirement for no duplication. You'd need that code in all classes.
The OP's problem is a classic example for model inheritance (Reservation would relate to the common base class). Since there is no model inheritance in the current developer version, you'd have to factor out the behaviour that makes something reservable into common class and delegate to this. class Reservable(models.Model): [...] class Reservation(models.Model): reserves = models.ForeignKey(Reservable) class Theater(models.Model): reservations = models.ForeignKey(Reservable) Now I can relate my reservation to a Reservable and I can put reservation-specific implementations (find_available_timeslot, etc.) into the Reservable class. I can also put together a simple calendar view for a resource's reservations, regardless of wether they're for a hotel, a restaurant, or whatever. Daniel --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
