Only design comments, user tables and so on. One person comments, another reply, then comment, and then reply
Reply to discussion (solution)
Don't know what your comments and responses mean
Since it is a forum, there must be a main post, all comments and replies are for the main (now popular style) so comments and replies should contain the ID of the main posts
If you need comments and responses for a comment and reply, you also need to include the corresponding ID for the comment and reply (this style is a tree form used in earlier forums)
Don't know what your comments and responses mean
Since it is a forum, there must be a main post, all comments and replies are for the main (now popular style) so comments and replies should contain the ID of the main posts
If you need comments and responses for a comment and reply, you also need to include the corresponding ID for the comment and reply (this style is a tree form used in earlier forums)
Just like csdn, I post, you comment on me, I reply you again, you reply to me again. This kind of data table how to design, do not understand
CSDN is the first solution.
ID Unique identification Word
The ID of the PID main stick
Other fields that you need
Can still be divided into two tables
Id
Other fields that you need
ID Unique identification Word
The ID of the PID main stick
Other fields that you need
The above can be said to drop, the main stick to have an ID, this ID is the main sticker ID in the comment, so that can be linked together
Another way is to build the building, you can press the time, but it is best to add a field, is the ID of the floor
Primary KEY comment Person ID reviewer ID timestamp comment content