Thanks!
I submitted a patch: https://github.com/django/django/pull/5963
If the reporter could test it and confirm that it fixes the issue, that would
be great.
--
Aymeric.
Hi,
On Fri, 08 Jan 2016, Aymeric Augustin wrote:
> I didn’t realize SQLITE_MAX_COLUMN would be the limit here.
>
> Would you mind opening a ticket on https://code.djangoproject.com/?
Done: https://code.djangoproject.com/ticket/26063
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Support Debian
Hi,
Raphael Hertzog wrote:
> Also does this also happen if you drop debug_toolbar from INSTALLED_APPS ?
It still happens without debug_toolbar.
> I have the feeling that this code path is only used when you actually want
> to print the SQL query that has been executed and this is usally only
> n
Hello Raphael,
Thanks for a great analysis. I can confirm this is a bug in Django.
I didn’t realize SQLITE_MAX_COLUMN would be the limit here.
Would you mind opening a ticket on https://code.djangoproject.com/?
(Alternatively I can do it.)
Best regards,
--
Aymeric.
> On 8 janv. 2016, at 10
[ CCing upstream Django developer to have its opinion ]
Hello,
On Fri, 08 Jan 2016, Christophe Siraut wrote:
> Sorry for the confusion, I have the same libsqlite3 version as you, and
> it is that one I recompiled with SQLITE_MAX_COLUMN 32767.
I can't reproduce the issue with Django 1.8. It looks
Hi,
On Mon, 28 Dec 2015, Christophe Siraut wrote:
> I am trying to run tracker configured with debian repositories using the
> sqlite
> backend, but several tasks are giving:
>
> OperationalError: too many columns in result set
Weird, the limit is at 2000 columns by default and I don't think
Package: tracker.debian.org
Severity: normal
I am trying to run tracker configured with debian repositories using the sqlite
backend, but several tasks are giving:
OperationalError: too many columns in result set
Tasks that are frequently failing:
UpdateRepositoriesTask
UpdatePackageBugSt
7 matches
Mail list logo
