#8 Logical separation of threads and replies

Отворено
отворено пре 4 година од abrax · 0 коментара
abrax коментирира пре 4 година

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`
Пријавите се да се прикључе у овом разговору.
Нема фазе
No Assignees
1 учесника
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
Откажи
Сачувај
Још нема садржаја.