Storing thread notifications in the database #56

Abierta
abierta hace 5 años por abrax · 0 comentarios
abrax comentado hace 5 años
Propietario

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.
Inicie sesión para unirse a esta conversación.
Sin Milestone
No asignados
1 participantes
Notificaciones
Fecha de vencimiento

0000-12-31

Dependencias

Esta incidencia actualmente no tiene ninguna dependencia.

Cargando…
Aún no existe contenido.