#56 Storing thread notifications in the database

오픈
abrax4 년 전을 오픈 · 0개의 코멘트
abrax 코멘트됨, 4 년 전

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.
로그인하여 이 대화에 참여
마일스톤 없음
No Assignees
참여자 1명
Due Date

Dec 31, 0000 Overdue

Dependencies

This issue currently doesn't have any dependencies.

Loading…
취소
저장
아직 콘텐츠가 없습니다.