#56 Storing thread notifications in the database

Aperto
aperto 4 anni fa da abrax · 0 commenti
abrax 4 anni fa ha commentato

Currently the database only stores hard facts about each thread. It doesn’t directly store booleans that basically amount to “should the user see this thread”. These are evaluated when list_thread is called.

It might simplify the code if I just add some boolean columns to the db, maybe they can even be auto-calculated (no computed columns in SQLite apparently). The cost would be a more stateful program with more side-effects.

The reason I’m concerned about this is the line if (mark != ' ') or (not interesting_only): in list_threads - it seems very hacky but I can’t improve on it either.

Currently the database only stores hard facts about each thread. It doesn't directly store booleans that basically amount to "should the user see this thread". These are evaluated when `list_thread` is called. It might simplify the code if I just add some boolean columns to the db, ~~maybe they can even be auto-calculated~~ (no computed columns in SQLite apparently). The cost would be a more stateful program with more side-effects. The reason I'm concerned about this is the line `if (mark != ' ') or (not interesting_only):` in `list_threads` - it seems very hacky but I can't improve on it either.
Effettua l'accesso per partecipare alla conversazione.
Nessuna milestone
No Assignees
1 Partecipanti
Data di scadenza

Dec 31, 0000 Scaduto

Dependencies

This issue currently doesn't have any dependencies.

Loading…
Annulla
Salva
Non ci sono ancora contenuti.