|
|
il y a 1 an | |
|---|---|---|
| src | il y a 1 an | |
| static | il y a 1 an | |
| templates | il y a 1 an | |
| tests | il y a 1 an | |
| .gitignore | il y a 1 an | |
| README.md | il y a 1 an | |
| config.py | il y a 1 an | |
| pyproject.toml | il y a 1 an | |
| requirements-dev.lock | il y a 1 an | |
| requirements-embeddings.lock | il y a 1 an | |
| requirements.lock | il y a 1 an | |
| settings.toml | il y a 1 an |
In the featured_article_snapshot_id view, the field featured_article_snapshot_id is taken as if it was unique by row, but it is not.
This can be easily checked with this query :
SELECT * FROM (
SELECT featured_article_snapshot_id, json_group_array(snapshot_id), COUNT(*) as count
FROM snapshot_apparitions
WHERE is_main -- Not required
GROUP BY featured_article_snapshot_id
)
WHERE count > 1
Among other things it leads to "deadends" while browsing the UI, likely because the timestamp search and time diff relies on this false assumption.