Klaas van Schelven a717dd7374 Truncate input-data that exceeds max_length ...

Avoiding any (1406, "Data too long for column ...") on MySQL.

For the 'plainly provided' fields I followed the documented maximums which are
also our DB maximums. For calculated_* I harmonized with what Sentry &
GlitchTip both do (and which was already partially reflected in the code), i.e.
128 and 1024.

2025-02-08 21:21:55 +01:00

..

migrations

Chache stored_event_count (on Issue and Projet)

2025-02-06 16:24:25 +01:00

templates/issues

Chache stored_event_count (on Issue and Projet)

2025-02-06 16:24:25 +01:00

__init__.py

The ugliest thing that could get a stacktrace on screen

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

admin.py

Chache stored_event_count (on Issue and Projet)

2025-02-06 16:24:25 +01: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

Chache stored_event_count (on Issue and Projet)

2025-02-06 16:24:25 +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

Truncate input-data that exceeds max_length

2025-02-08 21:21:55 +01:00

views.py

event.data getters

2025-02-07 17:09:36 +01:00