On Tue, Mar 23, 2010 at 5:26 AM, Russell Keith-Magee <freakboy3...@gmail.com > wrote:
> On Tue, Mar 23, 2010 at 5:53 AM, David Cramer <dcra...@gmail.com> wrote: > > One of the recent changes in trunk was a change to how querysets were > > cloned. Due to this, some old code we had is no longer working. This > > was a custom aggregate which relied on "aggregate_select" (see below). > > I believe the change I'm referring to is what is causing this, and I'm > > unsure of what the proper approach should be now. Should this also be > > considered a bug? If so, I'll go ahead and file a ticket. > > I can't think of any obvious reason that clone() behavior should have > changed, or why the aggregate you describe shouldn't be cloneable. I'm > not aware of any existing report in this area, either, so yes, this > should be reported as a bug. > > I'd guess it is due to this change: http://code.djangoproject.com/changeset/12830 Karen -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
