Do both. Have one table for entries, but include a ForeignKey to a class/table called Ministry (or Section, or Category, or whatever).
Then all your blog entries will be in one big table, but you will be able to request only the ones that fit the category you're interested in. To create a new page, just add a row to the Ministry table. When you enhance your blog entries, you'll be doing all of them at once. Todd On Fri, 2006-12-01 at 14:35 +0000, Eric Lake wrote: > Does anyone have a suggestion? > > On Nov 29, 9:24 pm, "Eric Lake" <[EMAIL PROTECTED]> wrote: > > I am working on a church site that will have multiple areas. There will > > be pages for each of the different ministries like music, singles, > > students, etc. I am wanting a blog like function for each of these > > pages where the responsible people will be able to log in to the admin > > site and add news to their page. > > > > My question is would it be better to create a separate table for each > > of the pages or a single on and then add a ministry field that would be > > filled in and then use a filter to show the correct information on each > > page? > > > > Here are my thoughts and correct me if I am wrong. > > > > 1) If it is all in one table then doing a search for information on the > > entire site would be easier. > > 2) If they are separated then adding a new page later would be done by > > just adding a new class to the model.py. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
