On Friday, 9 November 2012 00:31:39 UTC+1, Russell Keith-Magee wrote:
> If you can show a clear difference in behaviour between 1.3 and 1.4, then
> you've definitely found a bug. If you can log this in Trac (and mark it as
> a release blocker, since it's a change in behaviour), we can investigat
On Thu, Nov 8, 2012 at 9:44 PM, Chi Ho Kwok wrote:
> Hi devs,
>
> 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
Hi devs,
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, ad
