On Wed, Dec 16, 2009 at 6:51 AM, Russell Keith-Magee <freakboy3...@gmail.com> wrote: > No need for workaround docs - I've just uploaded an RC3 patch that > implements deferred fields.
Sweet! I love it when other people do my work for me... > The one gotcha on this patch is that it now requires that you request > the primary key when you retrieve an object. [...] > This is slightly more restrictive than Jacob's RC2 patch - but I think > the RC3 behaviour is preferable. I agree, and it actually opens up another use for raw() -- fetching lazy objects where you've just got the ID, say in a materialized view or whathaveyou. I'll probably make a change to the docs to emphasize that you need the primary key a bit more strongly, but I'm quite happy with this change. Thanks! Jacob -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
