#8 Logical separation of threads and replies

오픈
abrax4 년 전을 오픈 · 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…
취소
저장
아직 콘텐츠가 없습니다.