Re: Design Question - Extending a model

On Mon, Jan 11, 2010 at 12:00 PM, Igor wrote: > Thanks a lot - I didn't know about generic relations, and will > definitely look at them - right now :). I start thinking about extending models (and other DRY mode/db methods) when I see myself repetitively typing out

Re: Design Question - Extending a model

Thanks a lot - I didn't know about generic relations, and will definitely look at them - right now :). The minimal subset - and that's where I'm trying to follow DRY - boils down to a Title, a slug, Content HTML of the entry, maybe a couple more things - all are very much like what you would

Re: Design Question - Extending a model

My instinct is that you may be trying to be too generic. Without knowing more details, a "generic Entry" sounds a lot like .. a database record. :) Django's model.Model base class already does a great job at being easily extensible. Is there a specific minimal-but-interesting set of database

Design Question - Extending a model

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)