#56 Storing thread notifications in the database

Open
opened 3 years ago by abrax · 0 comments
abrax commented 3 years ago

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.
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Due Date

Dec 31, 0000 Overdue

Dependencies

This issue currently doesn't have any dependencies.

Loading…
Cancel
Save
There is no content yet.