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. -joe On 6/4/07, Lic. José M. Rodriguez Bacallao <[EMAIL PROTECTED]> wrote: > 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 > models so I don't have to repeat all of those attributes in all models. > Until now, I represented this situation like a Generalization/Specialization > relationship with a on-to-one relation but I don't want to use it due to > this relation is going to change in future versions of django so, I don't > know what to do, anyone could help me? > > > -- > Lic. José M. Rodriguez Bacallao > Informatics Science University > Habana-Cuba. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
