My take on this is that .extra and .raw are 'hacks' that only exist because
the existing functions of the ORM are too limited. There are a few changes
coming to extend the utility of .annotate (and .aggregate), along with the
Lookup and Transform APIs, that should solve 90% of use cases that
Sorry to reopen an old thread, but this was is indicated to do in the
ticket doc.
I think actually extra is a very helpful function and that join is a
missing part of it. I'm thinking especially about the admin part, where one
sometime wants to add count of foreign keys to the view. Since the
Even if it is a kludge, it still accomplishes something that .raw() cannot
(as Dan put forth). I think deprecating it in favor of raw doesn't make
much sense, since they are two different things.
On Mar 9, 2011 4:06 PM, "Dan Watson" wrote:
>
>
> On Tuesday, March 8, 2011
On Tuesday, March 8, 2011 6:16:26 PM UTC-5, Russell Keith-Magee wrote:
>
> On Wed, Mar 9, 2011 at 7:09 AM, Jacob Kaplan-Moss
> wrote:
> > On Tue, Mar 8, 2011 at 9:35 PM, bendavis78 wrote:
> >> I'd like to start a discussion on this since russelm closed
On Wed, Mar 9, 2011 at 7:09 AM, Jacob Kaplan-Moss wrote:
> On Tue, Mar 8, 2011 at 9:35 PM, bendavis78 wrote:
>> I'd like to start a discussion on this since russelm closed the
>> issue. There are a few other people that believe the issue should be
>>
On Tue, Mar 8, 2011 at 9:35 PM, bendavis78 wrote:
> I'd like to start a discussion on this since russelm closed the
> issue. There are a few other people that believe the issue should be
> left open. I've been using this patch for nearly two years, and have
> found it to
http://code.djangoproject.com/ticket/7231
I'd like to start a discussion on this since russelm closed the
issue. There are a few other people that believe the issue should be
left open. I've been using this patch for nearly two years, and have
found it to be useful in several different cases.