Grey out history entries with empty results

oysteikt commented

2025-07-03 22:36:49 +02:00

Owner

No description provided.

oysteikt added the ui/ux label 2025-07-03 22:36:49 +02:00

oysteikt added this to the Kanban project 2025-07-03 22:36:49 +02:00

oysteikt moved this to Mid pri in Kanban on 2025-07-07 12:12:42 +02:00

oysteikt moved this to Next Version in Kanban on 2025-07-17 01:16:33 +02:00

oysteikt commented

2025-11-13 08:26:09 +01:00

Author

Owner

In order not to redo searches for every single history entry, this should probably be stored with the search somehow. It should be possible to recalculate, if the underlying data or search algorithm changes.

oysteikt commented

2026-02-23 17:47:48 +01:00

Author

Owner

Some thoughts:

We can easily and performantly refill this information for all previous entries with an sql EXISTS query. But do we want to do this every time the database is updated? Would it be reasonable to keep old searches as empty until it is searched for again, and then we update the status? Maybe we even should store which version (see mugiten/jadb#10) the history entry was made with, so we could cache whether the calculation would need to be reperformed?

Some thoughts: We can easily and performantly refill this information for all previous entries with an sql `EXISTS` query. But do we want to do this every time the database is updated? Would it be reasonable to keep old searches as empty until it is searched for again, and then we update the status? Maybe we even should store which version (see https://git.pvv.ntnu.no/mugiten/jadb/issues/10) the history entry was made with, so we could cache whether the calculation would need to be reperformed?

oysteikt commented

2026-02-24 09:24:45 +01:00

Author

Owner

Possibly relevant to #104

Grey out history entries with empty results #91