Klaas van Schelven 9ee623de6b Add Event.grouping field and fill it ...

An event always has a single (automatically calculated) Grouping associated with it.
We add this info to the Event model (we'll soon display it in the UI, and as per the
now-removed comment it's simply the consistent thing to do)

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

..

management

Add some cleanup of objects to make_consistent command

2024-12-13 16:07:01 +01:00

migrations

Add Event.grouping field and fill it

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

templates/events

Remove unused base template

2024-04-05 10:13:56 +02:00

__init__.py

The ugliest thing that could get a stacktrace on screen

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

admin.py

Distinguish ingested_at and digested_at

2024-07-18 14:45:59 +02:00

apps.py

Setting of value: outside 'try'

2025-01-29 13:37:31 +01:00

factories.py

Add Event.grouping field and fill it

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

models.py

Add Event.grouping field and fill it

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

retention_insight.py

Distinguish ingested_at and digested_at

2024-07-18 14:45:59 +02:00

retention_simulator.py

Remove various non-TODOs

2024-09-13 10:05:22 +02:00

retention.py

Note that MySQL supports DELETE w/ LIMIT too

2024-10-09 09:58:47 +02:00

tests.py

Visualize trimmed data ('x items trimmed')

2024-12-18 17:05:26 +01:00

ua_stuff.py

UA parsing: deal with lists

2024-11-22 09:21:36 +01:00

urls.py

Add 'plain' view (Python-specific; only half-tested)

2024-03-30 23:10:18 +01:00

utils.py

Visualize trimmed data ('x items trimmed')

2024-12-18 17:05:26 +01:00

views.py

Become robust for lack of .values key in exception

2024-12-16 11:22:32 +01:00