From 81c85e3345175a0699f32c96b89ca2dd07758d69 Mon Sep 17 00:00:00 2001 From: alixz Date: Sun, 5 Oct 2025 21:06:35 +0000 Subject: [PATCH] Actualiser README.md --- README.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index ba4eec1..895bff7 100644 --- a/README.md +++ b/README.md @@ -30,4 +30,13 @@ CREATE TABLE interactions ( - "uwuClips" : user upscaled or interpolated clip, `count` indicates the number of clips processed. `framerate` is the framerate of the composition the user is working on. -`version` is uwu2x version (not After Effects version). \ No newline at end of file +`version` is uwu2x version (not After Effects version). + +## Ideas + +I believe the "solution" should feature : + +- a "script" that takes [1 ; N] rows and adds them to an "analytics-optimized" database. +Ideally, it should be able to process all existing rows and add future ones. Since database INSERT and UPDATE are expensive, the script should do a lot of "in-memory" processing : if there are two `uwuClips` interactions for the same user, do **not** do 2 `UPDATE` in the analytics database : instead, create an object (like Javascript object if your solution is written in Javascript) representing the user's profile, update it with both interactions, then perform 1 `UPDATE` in the database. + +- a second "script" to return statistics contained in the "analytics-optimized" database, like any user profile, total user count, active users per day, most used uwu2x version, most used uwu2x version over time, etc.