Changes between Initial Version and Version 2 of Ticket #19263


Ignore:
Timestamp:
Nov 13, 2012, 4:42:56 PM (11 years ago)
Author:
Aymeric Augustin
Comment:

I could reproduce the failure under PostgreSQL.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #19263

    • Property Component UncategorizedCore (Other)
    • Property Triage Stage UnreviewedAccepted
    • Property Type UncategorizedBug
  • Ticket #19263 – Description

    initial v2  
    1 I've noticed that after upgrading to Django 1.4, __in queries really don't like empty sets. Simple queries still work, like User.objects.filter(groups__in=[]), but most failures I've seen are with Paginators. I think this is the minimum set to cause a DatabaseError, create any app, add a models.py with:
     1I've noticed that after upgrading to Django 1.4, `__in` queries really don't like empty sets. Simple queries still work, like `User.objects.filter(groups__in=[])`, but most failures I've seen are with Paginators. I think this is the minimum set to cause a DatabaseError, create any app, add a models.py with:
    22
    33{{{#!python
Back to Top