Hosted version of the talk:
http://www.roadside-developer.com/talks/2013-12-12_MelbDjango_MTI.Performance/#/
[Thanks, Brenton!]
--
Curtis
On 7 June 2014 11:52, Curtis Maloney wrote:
> Can I draw your attention to Sebastian Vetter's investigation of the
> relative scalability of different mod
Can I draw your attention to Sebastian Vetter's investigation of the
relative scalability of different model polymorphism approaches :
https://github.com/elbaschid/talks/tree/master/2013-12-12_MelbDjango_MTI.Performance
Basically, the "select_related then resolve" approach [used in
django-model-ut
Don't know if it's a big patch at all. A polymorphic call could be like
this:
1. Check if the class is polymorphic by itself or by inheritance:
Traverse the inheritance D-Graph (we have to remember it's not a tree
anymore) starting from the current class - It would stop on (and not count)
mode
On Fri, Jun 6, 2014 at 6:49 AM, Luis Masuelli
wrote:
> What about integrating polymorphic features in the ORM? It's like having
> the features of django-polymorphic but in the core.
>
> The polymorphism could be acheved by:
> 1. Having contenttypes installed (this is a common pattern).
>
What about integrating polymorphic features in the ORM? It's like having
the features of django-polymorphic but in the core.
The polymorphism could be acheved by:
1. Having contenttypes installed (this is a common pattern).
2. Specifying a root (first ancestor) model class like:
clas
