Re: ModelManager behaviour for Proxy Models

2015-04-03 Thread Collin Anderson
Hi Mahmud, I personally really like the technique of having a "type" column in the base model. It allows you to query across all types but still get the correct subclass. However, I think the manager is a good place to handle this. You could have a manager that looks something like: objects =

Re: ModelManager behaviour for Proxy Models

2015-03-31 Thread Shai Berger
Hi Mahmud, On Tuesday 31 March 2015 16:17:52 mahmudul islam wrote: > I am not sure about the current development branch but last time I checked, > performing query on proxy models by default considers all the objects of > the parent/base class. If anyone is to consider only the objects of that > c

ModelManager behaviour for Proxy Models

2015-03-31 Thread mahmudul islam
I am not sure about the current development branch but last time I checked, performing query on proxy models by default considers all the objects of the parent/base class. If anyone is to consider only the objects of that class, he has to implement a custom modelmanager for that and use it. In