queryset.none() acts like queryset.all() when using a values_list in a filter

[orblivion]

I'm using PostgreSQL 9.1.6

This does not work as expceted:

In : User.objects.filter(id__in = Profile.objects.none().values_list('user_id', flat = True))
Out: [<User: xxx>, <User: yyy>...]

However without values_list, the similar works as expected:

In : User.objects.filter(profile__in = Profile.objects.none())
Out: []

Casting values_list to list works as expected:

In : User.objects.filter(id__in = list(Profile.objects.none().values_list('user_id', flat = True)))
Out: []

In fact values_list claims to be EmptyQuerySet of [], as expected:

In : Profile.objects.none().values_list('user_id', flat = True)
Out: []

And a manually empty QuerySet works:

In : User.objects.filter(id__in = Profile.objects.filter(blah__in = []).values_list('user_id', flat = True))
Out: []

[Aymeric Augustin]

This looks a lot like #17712, please reopen if it's a different issue.

[ubercore]

This actually isn't, afaict, a dupe of #17712. The key to this issue is using in with a ValuesListQuerySet, when the ValuesListQuerySet evaluates to an empty list. The WHERE clause is updated with the subquery, but the subquery itself doesn't get a WHERE clause, so it returns all rows:

WHERE "table_name"."lookup_field" IN (SELECT U0."lookup_field" FROM "other_table" U0)

The expected behavior would be:

WHERE "table_name"."lookup_field" IN (SELECT U0."lookup_field" FROM "other_table" U0 where "lookup_field" = 'lookup_value')

[ubercore]

Sorry, different problem, but this does appear to be fixed. Re-closing.