Klaas van Schelven 86e8c4318b Add indexes on fields on which we order and vice versa ...

Triggered by issue_event_list being more than 5s on "emu" (my 1,500,000 event
test-machine). Reason: sorting those events on non-indexed field. Switching
to a field-with-index solved it.

I then analysed (grepped) for "ordering" and "order_by" and set indexes
accordingly and more or less indiscriminately (i.e. even on tables that are
assumed to have relatively few rows, such as Project & Team).

2025-02-04 21:19:24 +01:00

..

migrations

Semi-manual squash-migrations

2025-02-03 16:06:17 +01:00

templates/issues

Show event.grouping.grouping_key in the event details UI

2025-01-31 16:16:47 +01:00

__init__.py

The ugliest thing that could get a stacktrace on screen

2023-11-04 21:02:04 +01:00

admin.py

Django admin forms: do not mess up my specially crafted fields please

2024-09-12 14:08:46 +02:00

apps.py

The ugliest thing that could get a stacktrace on screen

2023-11-04 21:02:04 +01:00

factories.py

Clarify a docstring

2024-07-18 15:13:08 +02:00

forms.py

Django admin forms: do not mess up my specially crafted fields please

2024-09-12 14:08:46 +02:00

models.py

Describe role of Grouping and how it relates to Issue

2025-01-31 15:25:18 +01:00

regressions.py

Rewrite comments on 'reopen' and 'issue_is_regression'

2024-09-17 23:01:41 +02:00

tests.py

Add Event.grouping field and fill it

2025-01-31 16:16:07 +01:00

urls.py

Navigation: fix for missing events

2024-07-19 11:03:08 +02:00

utils.py

Show 'handled' and 'mechanism' in the event details

2025-01-31 13:02:49 +01:00

views.py

Add indexes on fields on which we order and vice versa

2025-02-04 21:19:24 +01:00