Right, thanks a lot, Todd.
I guess I'm not *that* stupid after all... :) Phew! :D
I think I was actually using the wrong approach to building the
magazines. I mean, they should have been separate apps from the start.
Or else, every freaking article will be in a huge database table that
also house
If an issue belongs to only one magazine and an article belongs to only
one issue, then including both the magazine and the issue in the article
model is redundant, so if you can avoid it, I would.
On the other hand, I see your point that being able to quickly find the
right issue when you have e
> So an article can be in more than one issue of a magazine?
Not at all. The Article belongs to only one Issue, which is what I want
the ForeignKey to mean.
I just want to limit the choices of Issues to the ones that make sense,
i.e. to the Issues that belong to the chosen Magazine.
> Just over
So an article can be in more than one issue of a magazine?
My guess is that each article only appears in one issue. If that's the
case, you should only have the issue as a foreign key. The problem there
is that you may be annoyed that the issue is something like "June 2004".
Just override the iss
I'm stuck at what I think should have been one of the easiest steps of
building my magazines website: the models. :(
I really feel stupid for that, so please tell me the right way to do
this.
This is what I have: Magazines, with many Issues each, and articles,
which belong to only one Magazine, a
5 matches
Mail list logo
