another option could be use the contenttype framework, it's not well
documented but using the source and examples could help, take a look here
http://feh.holsman.net/articles/2006/06/03/django-contenttype to get an idea
about the framework and links to examples.
Regards,
Ali
On 6/4/07, Joseph He
If it's the *same* information, then use a foreign-key relationship.
If it's different information, then it needs to be stored separately,
and defining that on the models is a good way of doing that.
You can shoot yourself in the foot by trying to re-use too much as
well as too-little. It is ulti
that is repeating a lot of common information about my models, what about
DRY, reusing, etc?
On 6/4/07, Joseph Heck <[EMAIL PROTECTED]> wrote:
>
>
> Maybe a foreign key relationship would work, but you might just
> consider adding all those attributes to each model. Unless you think
> you'll end w
Maybe a foreign key relationship would work, but you might just
consider adding all those attributes to each model. Unless you think
you'll end with really sparse tables, it may be worth it for the
simplicity.
You wouldn't want to use a one-to-one table for common elements among
different models.
Hi for everyone. I'm stuck with django, I want to represent this situation:
I have a lot of content types like, news, images, urls, etc. All of them
have common attributres like creation date, expiration date, publication
date, title and so on. The problem is how to represent this with django
mode
5 matches
Mail list logo
