#8 Logical separation of threads and replies

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

If Issue #7 is supported, there should be a logical separation between threads and replies.

Currently, one can simply add the same thread twice with different anchors since URL is the primary key. But this would create problems when for instance calling ./lizard.py o. Individual replies should be grouped under their thread.

Alternatively the database should fundamentally track individual replies, not threads (if a thread is given, the OP post is tracked) and replies should be grouped together under threads when calling ./lizard.py l

If Issue #7 is supported, there should be a logical separation between threads and replies. Currently, one can simply add the same thread twice with different anchors since URL is the primary key. But this would create problems when for instance calling `./lizard.py o`. Individual replies should be grouped under their thread. Alternatively the database should fundamentally track individual replies, not threads (if a thread is given, the OP post is tracked) and replies should be grouped together under threads when calling `./lizard.py l`
Inicie sesión para unirse a esta conversación.
Sin Milestone
No Assignees
1 participantes
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Cargando…
Cancelar
Guardar
Aún no existe contenido.