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 pag
On 01-Dec-06, at 8:05 PM, Eric Lake wrote:
>> 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.
i would go for on
That sounds good. I will start playing around with this and see if I
can get something up with it. Thanks again for all of your help.
On Dec 1, 12:52 pm, "Guillermo Fernandez Castellanos"
<[EMAIL PROTECTED]> wrote:
> > It almost seems that I could do away with the MINISTRY_CHOICES piece
> > and j
> It almost seems that I could do away with the MINISTRY_CHOICES piece
> and just use the tags because if a tag name does not already exist the
> admin interface will allow one to be created from the Entries page. If
> that is the case then if I want a page to only display the posts for
> music (a
OK. So does the following code look like it would work the way that we
have been discussing?
from django.db import models
from django.contrib.auth.models import User
# Create your models here.
MINISTRY_CHOICES = (
('MUS', 'music'),
('SIN', 'singles'),
> Thank you. That is what I was thinking but I wanted to get others
> opinions first. This will also help stay with the DRY ideals. I guess
> the real difficult part would be if a new ministry is added to the
> list. If I understand how it works I would have to make changes in the
> model and then
Thanks for the comments. I am still in a planning phase and new to
django as well. I will have to wrap my head around the tag stuff but
these are great ideas.
On Dec 1, 11:13 am, "Guillermo Fernandez Castellanos"
<[EMAIL PROTECTED]> wrote:
> > Thank you. That is what I was thinking but I wanted t
On Dec 1, 9:59 am, "Eric Lake" <[EMAIL PROTECTED]> wrote:
> Thank you. That is what I was thinking but I wanted to get others
> opinions first. This will also help stay with the DRY ideals. I guess
> the real difficult part would be if a new ministry is added to the
> list. If I understand how it
Thank you. That is what I was thinking but I wanted to get others
opinions first. This will also help stay with the DRY ideals. I guess
the real difficult part would be if a new ministry is added to the
list. If I understand how it works I would have to make changes in the
model and then modify th
Cheers,
I would do it in a single table.
Maybe i would add a field to the Post like:
MINISTRY_CHOICES = (
('MUS', 'music'),
('SIN', 'singles'),
('STU', 'students'),
)
ministry = models.CharField(ma
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 t
11 matches
Mail list logo
