I have a model with blog-postings, assigned to a specific user - the user is stored in the table "posting" via foreignkey.
the user is part of a grade, part of a school and part of a state - all of which have overview-pages. so, to get all the postings for a state I have to do the following: 1. search for schools in that state 2. search for grades in that school 3. search for users within that grade 4. and finally, get all the postings for that user seems a little complicated. another way is to store grade, school and state in the postings- table. with that, the postings are a lot easier to retrieve. on the other hand, it seems a bit strange to store things twice (e.g. the user is assigned to a grade, so it´s kind of senseless to store the grade for a posting also). maybe someone can give me advice on which is the "better" solution. thanks, patrick --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
