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 houses articles from the other magazines. I think this is just wrong. The same would happen to sections: a long table of sections that aren't really related to each other, because each of them belongs to a different magazine. By separating magazines into different apps, I get everything I wanted: - separate database tables for each magazine - the user chooses the magazine, and only the valid issues and sections appear on the list Anyway, as a reply to your last (extremely helpful) msg: > 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. The thing is, when I put in an article, I might not have its section yet. Yes, I know, this is annoyingly complex and boring... > Is this something end users will need to get at? If so, I wouldn't > depend on the admin interface and would write my own view that would > allow someone to pick a magazine and then have another drop-down > (possibly updated using Ajax) that would be limited to its issues. When > you read the form, ignore the magazine and just record the issue. Yes, end users (the writing team) will use this Admin interface. Emphasizing on the "with deadlines" part of Django's motto, I have to be *really* *really* quick with this website. ;) So, no custom views at this moment. > If it's just you, add an ordering to issues that sorts by magazines and > dates (or whatever) and you can type the first few characters of the > magazine name to find yourself in the right general area. That's what I'd been using, but it felt plain wrong. Once again, thanks a lot! Phess --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
