#8 Logical separation of threads and replies

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

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`
Effettua l'accesso per partecipare alla conversazione.
Nessuna milestone
No Assignees
1 Partecipanti
Data di scadenza

Nessuna data di scadenza impostata.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
Annulla
Salva
Non ci sono ancora contenuti.