Malcolm Tredinnick wrote:
> On Fri, 2006-06-09 at 13:25 +0200, Gábor Farkas wrote:
>> Malcolm Tredinnick wrote:
>>> On Wed, 2006-06-07 at 11:34 +0100, David Reynolds wrote:
Hi,
I seem to remember reading either on the mailing list or IRC channel
that sub-classing doesn't
On 6/10/06, Ned Batchelder <[EMAIL PROTECTED]> wrote:
>
> I am still using 0.91, and have a question about this Model Inheritance
> issue in the current trunk. We use model inheritance in our code, but in a
> specialized way: only the derived classes are used concretely. The base
> classes are
On Fri, 2006-06-09 at 13:25 +0200, Gábor Farkas wrote:
> Malcolm Tredinnick wrote:
> > On Wed, 2006-06-07 at 11:34 +0100, David Reynolds wrote:
> >> Hi,
> >>
> >> I seem to remember reading either on the mailing list or IRC channel
> >> that sub-classing doesn't work at the moment, is that
Hello,
David Reynolds wrote:
> I can't recreate the behaviour that
> replaces_model='modelname' used to do. Is this going to be readded,
> or a better way of doing it added and what sort of timescales are on
> this?
I was just about to ask the same question: I need to add some fields to
the
It does not work currently. Ticket #1656 at djangoproject refers to
this:
http://code.djangoproject.com/ticket/1656
This is apparently one of the projects being covered by the Google
Summer of Code.
Some discussion of it is at:
http://code.djangoproject.com/wiki/ModelInheritance
I myself need
Hi,
I seem to remember reading either on the mailing list or IRC channel
that sub-classing doesn't work at the moment, is that correct? It
seems to work to some extent but I can't recreate the behaviour that
replaces_model='modelname' used to do. Is this going to be readded,
or a better
6 matches
Mail list logo
