Russ,
Really useful response, thanks.
I had thought about your third option but as I figured there'd be a
lot of empty fields I didn't give it much consideration. I might
actually go down that route until I have a better understanding of
generic relations.
Thanks again.
j.
On Jun 29, 2:20
On 6/28/07, Jamie Pittock <[EMAIL PROTECTED]> wrote:
>
> I don't want to code myself into a corner, so when I start looking at
> features such as allowing users to search all venues would I be best
> with one parent model or will I be ok keeping them separate? The
> different types of venues
I'm still new to Django so bear with me ;)
I have models for different types of venues (Bars, Clubs, etc).
Because for example, I'd like to use one Rating model across all these
venue Models I'd presumed that I'd need a parent Venue Model, using
some kind of one-to-one relationship (until model
3 matches
Mail list logo
