Mercurial > kallithea
view docs/usage/statistics.rst @ 7963:46681ae86693
db: introduce migration step after 93834966ae01 dropped non-nullable inherit_default_permissions
The database migration step was lazily and naively skipped ... but that turns
out to be a problem when new users are added.
In the database, the original column 'inherit_default_permissions' was
marked as non-nullable without default value. In the Kallithea code after
commit 93834966ae01, the column 'inherit_default_permissions' was no longer
known, and thus not given a value when new users are added. As a result, the
database complained:
IntegrityError: (psycopg2.errors.NotNullViolation) null value in column "inherit_default_permissions" violates not-null constraint
Fix that now by adding an appropriate db migration step to actually remove
the columns.
Use meta reflection to check if columns exist before running the upgrade
step. The upgrade step only has to be run if it is an old database - not if
it has been created after the schema changes were introduced.
For the downgrade step, make sure to set a default value for non-nullable
columns.
author | Mads Kiilerich <mads@kiilerich.com> |
---|---|
date | Sat, 23 Nov 2019 02:27:19 +0100 |
parents | 5ae8e644aa88 |
children |
line wrap: on
line source
.. _statistics: ===================== Repository statistics ===================== Kallithea has a *repository statistics* feature, disabled by default. When enabled, the amount of commits per committer is visualized in a timeline. This feature can be enabled using the ``Enable statistics`` checkbox on the repository ``Settings`` page. The statistics system makes heavy demands on the server resources, so in order to keep a balance between usability and performance, statistics are cached inside the database and gathered incrementally. When Celery is disabled: On each first visit to the summary page a set of 250 commits are parsed and added to the statistics cache. This incremental gathering also happens on each visit to the statistics page, until all commits are fetched. Statistics are kept cached until additional commits are added to the repository. In such a case Kallithea will only fetch the new commits when updating its statistics cache. When Celery is enabled: On the first visit to the summary page, Kallithea will create tasks that will execute on Celery workers. These tasks will gather all of the statistics until all commits are parsed. Each task parses 250 commits, then launches a new task.