Re: what to do instead of adding to Query.extra_where ?

On Sep 3, 2:10 am, Steve Holden wrote: > On 9/2/2010 1:44 AM, Paul Winkler wrote: > > > Hah. That was a pretty long message relative to how quickly I found > > the answer myself :-p > > Sorry for the noise. > > > For posterity, extra(where=...) is indeed the solution. I

Re: what to do instead of adding to Query.extra_where ?

On 9/2/2010 1:44 AM, Paul Winkler wrote: > Hah. That was a pretty long message relative to how quickly I found > the answer myself :-p > Sorry for the noise. > > For posterity, extra(where=...) is indeed the solution. I overlooked > the obvious: > the class I was trying to fix is itself a

Re: what to do instead of adding to Query.extra_where ?

Hah. That was a pretty long message relative to how quickly I found the answer myself :-p Sorry for the noise. For posterity, extra(where=...) is indeed the solution. I overlooked the obvious: the class I was trying to fix is itself a subclass of QuerySet. So given this line:

what to do instead of adding to Query.extra_where ?

Hi folks, I'm working on a codebase (a fork of http://code.google.com/p/ebcode/) that is supposed to be run against Django 1.1. It has several lines like this: clone.query.extra_where += ('db_newsitem.id = db_attribute.news_item_id',) That line raises a traceback like this: Traceback (most