Your message dated Mon, 20 Aug 2018 15:39:22 +0200
with message-id <20180820133922.ga8...@home.ouaza.com>
and subject line Re: Bug#809211: tracker.debian.org: sqlite backend not usable
has caused the Debian Bug report #809211,
regarding tracker.debian.org: sqlite backend not usable
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
809211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809211
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
UpdatePackageBugStats
UpdateLintianStatsTask
UpdateExcusesTask
UpdateBuildLogCheckStats
DebianWatchFileScannerUpdate
UpdateSecurityIssuesTask
UpdateUbuntuStatsTask
UpdateWnppStatsTask
I have tried the following with little success:
Use a small subset of repositories
Recompile libsqlite with #define SQLITE_MAX_COLUMN 32767
Hack the querysets like
http://stackoverflow.com/questions/7106016/too-many-sql-variables-error-in-django-witih-sqlite3
I think sqlite does not scale and we should not recommend it, in the setting
files:
# If you want to run a development setup close to what's running on
# tracker.debian.org, then uncomment the next two lines.
from .debian import *
- from .db_sqlite import DATABASES
+ from .db_postgresql import DATABASES
and remove db_sqlite.py.
Note we have a warning in the documentation:
Distro Tracker does not rely on any database specific features and as such
should be
able to run on top of any database server. The only possible known issue is
when
using sqlite3 which has a limit on the number of query parameters of 999 on
some systems.
Cheers,
Christophe
--- End Message ---
--- Begin Message ---
Hi,
On Sat, 09 Jan 2016, Raphael Hertzog wrote:
> 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
This has been fixed a long time ago and the current version of Django that
we recommend does not have the problem. I'm still actively using sqlite
for development and it works fine.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/
--- End Message ---
