On Thu, Mar 4, 2010 at 5:02 PM, Johannes Dollinger
wrote:
> Hi Steve,
>
> Multiple inheritance with abstract models works, and mostly did since the
> feature was added afaict. I use it regulary.
If multiple abstract inheritance works, it is accident, not intention.
For example, there is nothing i
Hi Johannes,
Yes inheriting the managers is in fact how I currently deal with the
situation however I feel as though this violates the DRY principle as
the relationship is already expressed via the model inheritance. I
guess "explicit is better than implicit" chimes in here to some
degree.
On Ma
Hi Steve,
Multiple inheritance with abstract models works, and mostly did since
the feature was added afaict. I use it regulary.
Just stay away from diamond inheritance and multi-multi-table
inheritance.
Regarding your managers: couldn't you just use inheritance explicitly?
class Manager
Hi Russel,
Thanks for your feedback. That's a really interesting position to
learn about with regard to multiple inheritance as I use it all the
time across basic abstract models without any issues.
The approach I was thinking of is very simplistic and possibly naive.
It appears as though I just
On Mon, Mar 1, 2010 at 12:40 PM, Stephen McDonald wrote:
> Hi there,
>
> I'm just getting an understanding around how managers from abstract
> models are applied to a subclass model and it appears as though if a
> model inherits from two abstract models that each define a manager
> with the same a
Hi there,
I'm just getting an understanding around how managers from abstract
models are applied to a subclass model and it appears as though if a
model inherits from two abstract models that each define a manager
with the same attribute name, eg "objects", then normal mro applies
and the derived
