#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`
登陆 并参与到对话中。
未选择里程碑
未指派成员
1 名参与者
到期时间

未设置到期时间。

依赖工单

此工单当前没有任何依赖。

正在加载...
取消
保存
这个人很懒,什么都没留下。