Article From:https://segmentfault.com/q/1010000012146580
Question:
Now we need to develop an article classification function. At present, there is a tentative three level classification. Considering the scalability of the classification, the table structure is designed as follows:
| field | type |
|---|---|
| id | char(32) |
| name | varcahr(50) |
| parentId | char(32) |
The question now is whether we need to save another hierarchical relationship, that is, to save the path, or to keep the depth of the tree.
Answer 0:
The article table:
id name type_id
Article ID name is classified as IDClassification table:
id name parent_id
Classified ID classification name classification of parent IDAnother way is to pull the type_id out of a table in the article to make a relational table.
art_id type_id Personal comparison recommends second ways to store the relationship separately and facilitate maintenance.
Similar Posts:
- EasyUI infinite level classification table design and code development 1 (data table structure design)
- EasyUI infinite level classification table design and code development 1 (data table structure design)
- How should database design relate to data (mongodb)??
- EasyUI infinite level classification table design and code development 2 (program code logic)
- EasyUI infinite level classification table design and code development 2 (program code logic)
- How is the classification label stored in the database?
- DotNet unlimited introduction of rookie entry (1) design
- How is the classification label stored in the database?
- The problem of the usage of the laravel model
- [mysql] how do I query the specified articles from the following two related tables?
Link of this Article:
How to design the data table structure of the classification table