Hi, I'm modeling book structures. Currently I have Chapter objects that belong (ForeignKey) to a Book and each Chapter has sequence number so the book can know how to order the chapters within itself. That was okay until I realized the chapters can be shared between books.
For me that looks a little complex. The 'sequence' doesn't really belong to the Chapter or the Book, but to their relationship. A Chapter may have one sequence number when part of Book A, and another for Book B. Arggg. I used to write my configuration files in XML format, where order counts. Moving to SQL is nice, but there are definitely things I haven't thought of before. How do you handle a property that belongs to a relationship? A manager of some sort? thanks, --Tim Arnold -- 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.
