Hi all, This is a general question for whoever is good with best practices for Django design (software design that is).
I'd like to implement (well, kinda have implemented), a generic Entry object that would be good for several uses. For example, an Event (such as, say, a website presentation) is just an Entry with one or more start/end dates attached. A business listing in a catalogue is basically an Entry with some other properties such as business rating or whatever else. There's more to it but I think you get the idea - I want the Entry to be EASILY extensible with more features. This includes easily extending the templates if possible. Am I trying to be too generic? Or, if not, what's a good approach to take - I can use model inheritance, or an Event model could have an Entry as a Foreign Key (which is what it does now). Or maybe there's a whole other approach that I've missed but everyone else does? In any case, how difficult would it be to access, say, all events that have a post, or the other way around? I'm sorry if I'm not precise or if this sounds stupid. I have a great trust in Django, but so far I've been advancing a bit slowly. It would be great to hear your opinions. Thanks, Igor
-- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
