On 25 September 2012 17:45, Alex Ogier wrote:
> There's a big thing you cannot do without grouping models: you can't have
> an abstract base class relate to another abstract base class. Django's
> foreign key mechanism doesn't know how to relate to a to-be-instantiated
>
On Mon, Sep 24, 2012 at 12:33 PM, Daniel Sokolowski <
daniel.sokolow...@klinsight.com> wrote:
> It also seems the current abstract model mechanism can do everything a
> model library can minus the model prefixing and the model grouping; that
> though I would just tackle using a naming
Hi Jonathan, I am undecided on this one, when I first looked at it I thought it
was a great idea but now I feel it would be more problematic to read and
traverse and update such code due to the ModelFactory > MyModelFactory >
MyModels logic flow. It feels a lot like using class based views –
On Mon, Sep 24, 2012 at 9:55 AM, Jonathan Slenders
wrote:
> Hi everyone,
>
> This may be interesting to some of you. I created a small library for
> inheritance of a set of models.
> It's best to go quickly through the Readme on the site below.
>
> We felt a need for
> On 24 syys, 16:55, Jonathan Slenders
> wrote:
>> This may be interesting to some of you. I created a small library for
>> inheritance of *a set of* models.
>> It's best to go quickly through the Readme on the site below.
>>
>> We felt a need for this, but I'm
On 24 syys, 16:55, Jonathan Slenders
wrote:
> This may be interesting to some of you. I created a small library for
> inheritance of *a set of* models.
> It's best to go quickly through the Readme on the site below.
>
> We felt a need for this, but I'm wondering