QuerySet generating wrong SQL

I'm having a problem when I try to create a queryset with a call to filter() and extra(). No matter what operator I use when generating the expression I end up with an SQL query that ANDs the filter() and extra() parameters, rather than ORing them. Example: <<< code >>> class ProjectManager(m

Different results for same queryset on devserver and testserver

Hi, I'm experiencing the weirdest of errors with one of my tests. What happens is the following: I create a queryset by on a model that has (among other fields) an 'author' and a 'public' field. I want to limit an anonymous user to only view those instances marked as "public=True", so I do the usu

Re: Different results for same queryset on devserver and testserver

By the way, I forgot to point out that this is actually a GeoQuerySet, so that might explain the rarity of the issue. Cheers, David On Jul 26, 2:16 pm, innervision wrote: > Hi, > > I'm experiencing the weirdest of errors with one of my tests. What > happens is the following: I