#8 Logical separation of threads and replies

Atvērta
abrax atvēra pirms 4 gadiem · 0 komentāri
abrax komentēja pirms 4 gadiem

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`
Pierakstieties, lai pievienotos šai sarunai.
Nav atskaites punktu
Nav atbildīgo
1 dalībnieki
Izpildes termiņš

Izpildes termiņš nav uzstādīts.

Atkarības

Šai problēmai pagaidām nav nevienas atkarības.

Notiek ielāde…
Atcelt
Saglabāt
Vēl nav satura.