Re: Odd behavior on proxy models should be on documentation

This looks exactly as I expect. Proxy models are not distinct in the database from their parent models, they are just python wrappers around them. It is documented and expected that creating instances of the parent class creates instances of the proxy class. Since creating an instance of a

Odd behavior on proxy models should be on documentation

Hi there. I was working with proxies models and I found an odd behavior on a QuerySet, and I ask here whether it should be documented. Consider the following code: from django.db import models #from model_utils.managers import InheritanceManager class Generic(models.Model): pass #

Re: Usage and documentation of F()

If, at the same time, perhaps ExpressionNode got a mention too, that could really open up some opportunities :) On 17 August 2013 21:17, Some Developer wrote: > On 14/08/13 10:05, Marc Tamlyn wrote: > >> (Disclaimer: I didn't write any of this code, I'm just working

Re: Usage and documentation of F()

On 14/08/13 10:05, Marc Tamlyn wrote: (Disclaimer: I didn't write any of this code, I'm just working from my own possibly flawed understanding) The main point of using F is not generally for performance per se, rather for database consistency. In the first example, the performance increase is

Re: Changes in Model._meta

On Sat, Aug 17, 2013 at 08:34:27AM +0700, Russell Keith-Magee wrote: > > 1) There are now more fields in _meta.fields, obviously. For each > >ForeignKey there is now an extra field with `_id` appended to its > >name. This extra field is not editable nor serializable, which > >means