blocks|key|857106|text|布尔列卖家或非卖家|type|unstyled|depth|inlineStyleRanges|entityRanges|data|857107|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

blocks|key|1878799|text|您可以这样做，其中TelephonePerson包含用于customerId和TelephoneId的可能为空的列；|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1878800|Customer+Table:
++++Id
++++*whatever+customer+details+exist*

Seller+Table:
++++ID
++++*whatever+seller+details+exist*

TelephonePerson:
++++SellerId
++++CustomerId
++++TelephoneId

Telephone:
++++ID
++++Phone+Number|code-block|syntax|javascript|1878801|或者，为了避免额外的表，你可以这样做，在你的电话桌上有linkId和PersonTypeId。PersonTypeId指的是卖家或客户，根据这一点，您可以加入到linkId上相应的表中；|1878802|Customer+Table:
++++Id
++++*whatever+customer+details+exist*

Seller+Table:
++++ID
++++*whatever+seller+details+exist*

Telephone:
++++ID
++++Phone+Number
++++LinkId
++++PersonTypeId|1878803|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

You could do it like this, where TelephonePerson contains potentially nullable columns for customerId and TelephoneId;

<pre><code>Customer Table:
 Id
 *whatever customer details exist*

Seller Table:
 ID
 *whatever seller details exist*

TelephonePerson:
 SellerId
 CustomerId
 TelephoneId

Telephone:
 ID
 Phone Number
</code></pre>

Alterntaively, to avoid the extra table, you could do it like this, where you have linkId and PersonTypeId on your telephone table. The PersonTypeId would refer to either sellers or customers, and based on what that is you join onto the appropriate table on the linkId;

<pre><code>Customer Table:
 Id
 *whatever customer details exist*

Seller Table:
 ID
 *whatever seller details exist*

Telephone:
 ID
 Phone Number
 LinkId
 PersonTypeId
</code></pre>

blocks|key|5290927|text|最灵活的方法可能如下所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5290928|首先创建一个中立的电话号码表。|5290929|Phone+Numbers:
++#+Id
++++Phone+Number
++++Prefix|code-block|syntax|javascript|5290930|为您的每个联系人(卖家、客户等)创建一个N-to-N表。|5290931|Sellers
++#+Id
++++other+fields...
Seller+Phone+Numbers
++#+Phone+Number+Id
++#+Seller+Id

Customers
++#+Id
++++other+fields...
Customer+Phone+Numbers
++#+Phone+Number+Id
++#+Customer+Id|5290932|这样：|5290933|5290934|稍后您可以使用相同的模式添加一个新表|unordered-list-item|5290935|卖家和客户都可以有一个共同的电话号码|5290936|您可以管理比计划的多一点的表。|5290937|5290938|entityMap^0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|11|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|12|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|13|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|14|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|15|8|@]|9|@]|A|$]]|$1|P|3|Q|5|R|7|16|8|@]|9|@]|A|$]]|$1|S|3|T|5|R|7|17|8|@]|9|@]|A|$]]|$1|U|3|V|5|R|7|18|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|19|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|Y|$]]

The most flexible way might be the following: 

First create a neutral phone numbers table.

<pre><code>Phone Numbers:
 # Id
 Phone Number
 Prefix
</code></pre>

For each of your contact (seller, customer, whatever), create a N-to-N table.

<pre><code>Sellers
 # Id
 other fields...
Seller Phone Numbers
 # Phone Number Id
 # Seller Id

Customers
 # Id
 other fields...
Customer Phone Numbers
 # Phone Number Id
 # Customer Id
</code></pre>

This way:

<ul>
<li>you can later add a new table using the same pattern</li>
<li>a seller and a customer can both have a common phone number</li>
<li>You get to manage a bit more tables than planned. </li>
</ul>

blocks|key|1878843|text|您使用一个普通的person表对其进行建模，如果该person既是一个客户又是一个卖家，那么他将在这两个表中使用相同的id。他也将仅在与personID关联的电话、地址等中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1878844|Person:
++++PersonID
++++*Details+common+to+all+people
Customer:
+++++PersonID
+++++*whatever+customer+details+exist*++
Sellere:
+++++PersonID
+++++*whatever+seller+details+exist*++
TelephonePerson:
+++++PersonId
+++++TelephoneId+
Telephone:
+++++PersonID
+++++Phone+Number+|code-block|syntax|javascript|1878845|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

You model it with a common person table and if the person is both a customer and a selelr he will be in both tables with the same id. He will also only be in phone, address, etc associated with the personID.

<pre><code>Person:
 PersonID
 *Details common to all people
Customer:
 PersonID
 *whatever customer details exist* 
Sellere:
 PersonID
 *whatever seller details exist* 
TelephonePerson:
 PersonId
 TelephoneId 
Telephone:
 PersonID
 Phone Number 
</code></pre>

I have table customer, table seller; and every customer have many phone-numbers, as seller do to. And I decide to do new table: Telephone, with IdTelephone, Prefix, Number, and IdCustomer or IdSeller, i don't know how to identify it, becouse IdCustomer could be same as IdSeller, how to solve this?
Mysql...

How to plan such database with maybe same id?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我有桌上的顾客，有桌子的卖家，每个顾客都有许多电话号码，卖家也一样。我决定做一个新的表:电话，有IdTelephone，前缀，号码，IdCustomer或IdSeller，我不知道如何识别它，因为IdCustomer可能与IdSeller相同，如何解决这个问题？Mysql...

问如何规划可能具有相同id的数据库？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何规划可能具有相同id的数据库？EN