


How to design the mysql table structure for nested display of article comments (in the form of NetEase news comments)
Now there is a post table (the structure cannot be changed)
tid topic pid
pid reply id
Now a new comment nesting display function is added, that is, tid=1
a commented a comment with a pid of 1
b replied to a's comment with a pid of 2
c replied to b's comment with a pid of 3
d replied to a with a pid of 3 4
Displayed as
1st floor pid1
2nd floor pid1,pid2
3rd floor pid1,pid2,pid3
4th floor pid1,pid4
That is, every reply to others needs to quote all previous replies.
(The format is the same as the comments on NetEase News)
I currently think of a structure that is post_conversation pid, to_pid
In this way, the 2nd floor reply will insert 2,1
<code> 3楼回复就插入两条 3,1 3,2 4楼回复就插入 4,1 </code>
If there is a conversation on the 99th floor, 98 pieces of data must be inserted
<code>这样有个好处就是可以很方便取出任意一个pid的评论情况 select topid from post_conversation where pid = 'xxx' order by pid ; 但是会造成多的重复数据 一个99楼对话得插入1+2+3+。。。+99条 </code>
If post_conversation is designed like this
pid, parent_pid (the pid being replied to)
The amount of data is small (only one message is inserted for each reply);
But querying all conversations for each pid is very troublesome (I am thinking of recursive query database);
<code>select parent_pid from post_conversation where pid = 'xxx' select parent_pid from post_conversation where pid = 'parent_pid ' ... 一直到parent_pid 为0为止,查询出所有的对话pid </code>
Do you have any good suggestions?
Reply content:Now there is a post table (the structure cannot be changed)
tid topic pid
pid reply id
a commented a comment with a pid of 1
b replied to a's comment with a pid of 2
c replied to b's comment with a pid of 3
d replied to a with a pid of 3 4
1st floor pid1
2nd floor pid1,pid2
3rd floor pid1,pid2,pid3
4th floor pid1,pid4
That is, every reply to others needs to quote all previous replies.
(The format is the same as the comments on NetEase News)
I currently think of a structure that is post_conversation pid, to_pid
In this way, the 2nd floor reply will insert 2,1
<code> 3楼回复就插入两条 3,1 3,2 4楼回复就插入 4,1 </code>
<code>这样有个好处就是可以很方便取出任意一个pid的评论情况 select topid from post_conversation where pid = 'xxx' order by pid ; 但是会造成多的重复数据 一个99楼对话得插入1+2+3+。。。+99条 </code>
pid, parent_pid (the pid being replied to)
The amount of data is small (only one message is inserted for each reply);
But querying all conversations for each pid is very troublesome (I am thinking of recursive query database);
<code>select parent_pid from post_conversation where pid = 'xxx' select parent_pid from post_conversation where pid = 'parent_pid ' ... 一直到parent_pid 为0为止,查询出所有的对话pid </code>
Thanks for the invitation
I used to use the most primitive recursive query method to achieve infinite nesting (menus, comments). Later, I saw an article posted by the administrator in the Laravel-China community, the article address is https://laravel-china.org/topics/2124, using the
pre-sorted traversal tree algorithm (Nested set model)
to achieve infinite tree levels Model (tag system, menu system, comment system, etc.). The subject can refer to the following.
One article corresponds to multiple comments, and one comment corresponds to multiple replies.
Q&A communities segmentfault.com and Tencent News They all use "reply to comments".
Take segmentfault as an example:
The questioner (poster) posted a question, and this question has multiple answers (layer owners), which is a one-to-many relationship in the database.
Each An answer can have multiple replies, which is also a one-to-many relationship.
<code>question(id, user_id,content) answer (id,question_id,user_id,content) reply (id,answer_id, user_id,content)</code>

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics











MySQL and phpMyAdmin are powerful database management tools. 1) MySQL is used to create databases and tables, and to execute DML and SQL queries. 2) phpMyAdmin provides an intuitive interface for database management, table structure management, data operations and user permission management.

IIS and PHP are compatible and are implemented through FastCGI. 1.IIS forwards the .php file request to the FastCGI module through the configuration file. 2. The FastCGI module starts the PHP process to process requests to improve performance and stability. 3. In actual applications, you need to pay attention to configuration details, error debugging and performance optimization.

In MySQL, the function of foreign keys is to establish the relationship between tables and ensure the consistency and integrity of the data. Foreign keys maintain the effectiveness of data through reference integrity checks and cascading operations. Pay attention to performance optimization and avoid common errors when using them.

The main difference between MySQL and MariaDB is performance, functionality and license: 1. MySQL is developed by Oracle, and MariaDB is its fork. 2. MariaDB may perform better in high load environments. 3.MariaDB provides more storage engines and functions. 4.MySQL adopts a dual license, and MariaDB is completely open source. The existing infrastructure, performance requirements, functional requirements and license costs should be taken into account when choosing.

SQL is a standard language for managing relational databases, while MySQL is a database management system that uses SQL. SQL defines ways to interact with a database, including CRUD operations, while MySQL implements the SQL standard and provides additional features such as stored procedures and triggers.

MySQL is suitable for rapid development and small and medium-sized applications, while Oracle is suitable for large enterprises and high availability needs. 1) MySQL is open source and easy to use, suitable for web applications and small and medium-sized enterprises. 2) Oracle is powerful and suitable for large enterprises and government agencies. 3) MySQL supports a variety of storage engines, and Oracle provides rich enterprise-level functions.

Multiple calls to session_start() will result in warning messages and possible data overwrites. 1) PHP will issue a warning, prompting that the session has been started. 2) It may cause unexpected overwriting of session data. 3) Use session_status() to check the session status to avoid repeated calls.

MySQL and phpMyAdmin can be effectively managed through the following steps: 1. Create and delete database: Just click in phpMyAdmin to complete. 2. Manage tables: You can create tables, modify structures, and add indexes. 3. Data operation: Supports inserting, updating, deleting data and executing SQL queries. 4. Import and export data: Supports SQL, CSV, XML and other formats. 5. Optimization and monitoring: Use the OPTIMIZETABLE command to optimize tables and use query analyzers and monitoring tools to solve performance problems.
