blocks|key|1370630|text|我在公司中使用它的方式是，我有一个Category表，一个Brands表和一个Products表(这是基本设置，我有更多用于价格历史、产品历史等的表)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1370631|Products表是主表，包含每个Categories和Brands的外键。|1370632|表tbl_category和tbl_brand具有相同的结构：|1370633|%2B-------%2B--------------%2B------%2B-----%2B---------%2B----------------%2B
%7C+Field+%7C+Type+++++++++%7C+Null+%7C+Key+%7C+Default+%7C+Extra++++++++++%7C
%2B-------%2B--------------%2B------%2B-----%2B---------%2B----------------%2B
%7C+id++++%7C+int(11)++++++%7C+NO+++%7C+PRI+%7C+NULL++++%7C+auto_increment+%7C
%7C+name++%7C+varchar(100)+%7C+YES++%7C+++++%7C+NULL++++%7C++++++++++++++++%7C
%2B-------%2B--------------%2B------%2B-----%2B---------%2B----------------%2B|code-block|syntax|javascript|1370634|表tbl_product|1370635|%2B-----------%2B---------------%2B------%2B-----%2B---------%2B----------------%2B
%7C+Field+++++%7C+Type++++++++++%7C+Null+%7C+Key+%7C+Default+%7C+Extra++++++++++%7C
%2B-----------%2B---------------%2B------%2B-----%2B---------%2B----------------%2B
%7C+id++++++++%7C+int(11)+++++++%7C+NO+++%7C+PRI+%7C+NULL++++%7C+auto_increment+%7C
%7C+category++%7C+int(11)+++++++%7C+YES++%7C+MUL+%7C+NULL++++%7C++++++++++++++++%7C
%7C+brand+++++%7C+int(11)+++++++%7C+YES++%7C+MUL+%7C+NULL++++%7C++++++++++++++++%7C
%7C+spec++++++%7C+varchar(100)++%7C+YES++%7C+++++%7C+NULL++++%7C++++++++++++++++%7C
%7C+descript++%7C+varchar(1000)+%7C+YES++%7C+++++%7C+NULL++++%7C++++++++++++++++%7C
%7C+unit++++++%7C+varchar(10)+++%7C+YES++%7C+++++%7C+PÇ++++++%7C++++++++++++++++%7C
%7C+cost++++++%7C+decimal(16,2)+%7C+YES++%7C+++++%7C+NULL++++%7C++++++++++++++++%7C
%7C+..................................................................%7C
%7C+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++%7C
%2B-----------%2B---------------%2B------%2B-----%2B---------%2B----------------%2B|1370636|我有下面的外键|BOLD|1370637|++KEY+`product_category_fk`+(`category`),
++KEY+`product_brand_fk`+(`brand`),
++CONSTRAINT+`product_brand_fk`+FOREIGN+KEY+(`brand`)+REFERENCES+`tbl_brand`+(`id`)+ON+UPDATE+CASCADE,
++CONSTRAINT+`product_category_fk`+FOREIGN+KEY+(`category`)+REFERENCES+`tbl_category`+(`id`)+ON+UPDATE+CASCADE|1370638|我使用的理由是：任何给定的产品都只有一个类别和一个品牌，所以我可以将这些信息放入产品记录本身。|1370639|​|1370640|这是一个很好的示例起点(取自这里)|1370641|1370642|1370643|📷|atomic|1370644|1370645|entityMap|0|LINK|mutability|MUTABLE|url|http://www.devcity.net/PrintArticle.aspx?ArticleID=186|1|IMAGE|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/dc19c22ff07f3f0d4153e0f9742eb3cc.png|imageAlt^0|H|8|T|6|13|8|0|0|8|H|A|S|6|0|1|C|E|9|0|0|1|B|0|0|5|2|0|0|8|J|0|0|E|2|0|0|0|0|0|1|1|0|0^^$0|@$1|2|3|4|5|6|7|1N|8|@$9|1O|A|1P|B|C]|$9|1Q|A|1R|B|C]|$9|1S|A|1T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1U|8|@$9|1V|A|1W|B|C]|$9|1X|A|1Y|B|C]|$9|1Z|A|20|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|21|8|@$9|22|A|23|B|C]|$9|24|A|25|B|C]]|D|@]|E|$]]|$1|J|3|K|5|L|7|26|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|27|8|@$9|28|A|29|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|L|7|2A|8|@]|D|@]|E|$M|N]]|$1|S|3|T|5|6|7|2B|8|@$9|2C|A|2D|B|U]]|D|@]|E|$]]|$1|V|3|W|5|L|7|2E|8|@]|D|@]|E|$M|N]]|$1|X|3|Y|5|6|7|2F|8|@$9|2G|A|2H|B|U]]|D|@]|E|$]]|$1|Z|3|10|5|6|7|2I|8|@]|D|@]|E|$]]|$1|11|3|12|5|6|7|2J|8|@]|D|@$9|2K|A|2L|1|2M]]|E|$]]|$1|13|3|10|5|6|7|2N|8|@]|D|@]|E|$]]|$1|14|3|10|5|6|7|2O|8|@]|D|@]|E|$]]|$1|15|3|16|5|17|7|2P|8|@]|D|@$9|2Q|A|2R|1|2S]]|E|$]]|$1|18|3|10|5|6|7|2T|8|@]|D|@]|E|$]]|$1|19|3|-4|5|6|7|2U|8|@]|D|@]|E|$]]]|1A|$1B|$5|1C|1D|1E|E|$1F|1G]]|1H|$5|1I|1D|1J|E|$1K|1L|1M|-4]]]]

The way I use it in my company is I have a <code>Category</code> table just as you have, a <code>Brands</code> table and a <code>Products</code> table (this is the basic setup, I have more tables for price history, product history, etc).

The <code>Products</code> table is the primary one, containing a foreign key to each of <code>Categories</code> and <code>Brands</code>.

Table <code>tbl_category</code> and <code>tbl_brand</code> has the same structure:

<pre><code>+-------+--------------+------+-----+---------+----------------+
| Field | Type | Null | Key | Default | Extra |
+-------+--------------+------+-----+---------+----------------+
| id | int(11) | NO | PRI | NULL | auto_increment |
| name | varchar(100) | YES | | NULL | |
+-------+--------------+------+-----+---------+----------------+
</code></pre>

Table <code>tbl_product</code>:

<pre><code>+-----------+---------------+------+-----+---------+----------------+
| Field | Type | Null | Key | Default | Extra |
+-----------+---------------+------+-----+---------+----------------+
| id | int(11) | NO | PRI | NULL | auto_increment |
| category | int(11) | YES | MUL | NULL | |
| brand | int(11) | YES | MUL | NULL | |
| spec | varchar(100) | YES | | NULL | |
| descript | varchar(1000) | YES | | NULL | |
| unit | varchar(10) | YES | | PÇ | |
| cost | decimal(16,2) | YES | | NULL | |
| ..................................................................|
| |
+-----------+---------------+------+-----+---------+----------------+
</code></pre>

And I have the following foreign keys:

<pre><code> KEY `product_category_fk` (`category`),
 KEY `product_brand_fk` (`brand`),
 CONSTRAINT `product_brand_fk` FOREIGN KEY (`brand`) REFERENCES `tbl_brand` (`id`) ON UPDATE CASCADE,
 CONSTRAINT `product_category_fk` FOREIGN KEY (`category`) REFERENCES `tbl_category` (`id`) ON UPDATE CASCADE
</code></pre>

The reasoning I used is: any given product has only one category and one brand, so I can put that information in the product record itself.

<hr>
This is a good example starting point (Taken from <a href="http://www.devcity.net/PrintArticle.aspx?ArticleID=186" rel="nofollow noreferrer">here</a>)

<a href="https://i.stack.imgur.com/3t3Ij.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/3t3Ij.png" alt=""></a>

I have two tables in MySql Workbench; Categories and Products. I created a third table which contains PK's from the first two tables. How do I sort out which product falls under which category. Do I need to create a fourth table? Also, it is obvious that one category has many products. How do I put this data into the table?

MySQL Workbench; creating intermediate tables and mapping them

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我在MySql工作台中有两个表:类别和产品。我创建了第三个表，其中包含来自前两个表的PK。我如何分类哪些产品属于哪一类。我需要创建第四个表吗？而且，很明显，一个类别有许多产品。如何将这些数据放入表中？

MySQL工作台；创建中间表并映射它们-腾讯云开发者社区-腾讯云

问MySQL工作台；创建中间表并映射它们
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问MySQL工作台；创建中间表并映射它们EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问MySQL工作台；创建中间表并映射它们
EN