On Mon, 2008-12-22 at 22:17 -0800, George Sakkis wrote:
[...]
> 1. With explicit concrete inline admin classes, the interface shows
> one section per class ("Book reviews", "Movie reviews", etc.). This
> might be a feature under some circumstances (you get a "group by
> review type" for free), bu
On Dec 22, 7:04 pm, Malcolm Tredinnick
wrote:
> On Mon, 2008-12-22 at 09:42 -0800, George Sakkis wrote:
>
> [...]
>
>
>
> > Unfortunately it doesn't work for what I tried. What I am trying to do
> > is have the Child classes as InlineModelAdmin in some other class that
> > references them. Here'
On Mon, 2008-12-22 at 09:42 -0800, George Sakkis wrote:
[...]
> Unfortunately it doesn't work for what I tried. What I am trying to do
> is have the Child classes as InlineModelAdmin in some other class that
> references them. Here's a sample:
>
> # === models.py ===
> class R
On Dec 21, 10:02 pm, Malcolm Tredinnick
wrote:
> On Sun, 2008-12-21 at 18:50 -0800, George Sakkis wrote:
> > Hi all,
>
> > I have a situation which I think would best be modeled as (single)
> > inheritance, involving product reviews for various kinds of products.
> > Naturally, there are some fi
On Sun, 2008-12-21 at 18:50 -0800, George Sakkis wrote:
> Hi all,
>
> I have a situation which I think would best be modeled as (single)
> inheritance, involving product reviews for various kinds of products.
> Naturally, there are some fields which are common to all reviews
> (overall rating, us
Hi all,
I have a situation which I think would best be modeled as (single)
inheritance, involving product reviews for various kinds of products.
Naturally, there are some fields which are common to all reviews
(overall rating, user, review date) and some which are specific to the
type of product.
6 matches
Mail list logo
