想问下自增主键的Id类型可以改为BigInt吗

[SirCFC]

问题在于，我修订了代码，处理了ID跳变的问题，但是ID跳变久了可能会超过ID的11位限制，所以想咨询下，如果数据库改为Bigint，代码需要调整吗

[dosubot]

Hey @SirCFC! 👋 I'm here to help you with any questions or issues you have. I'm a bot designed to help you solve bugs, answer questions, and become a contributor. Let me know how I can assist you!

当前数据库模式中，自增主键 ID 的数据类型在某些表中是 int(10) unsigned，而在其他表中是 int(11) unsigned ^{[1][2][3][4][5]}。如果将其更改为 BigInt，可能需要检查以下几个方面：

1. 应用代码：需要查看应用代码中是否有对 ID 字段的显式类型检查或转换，这些可能需要更新以支持 BigInt。

2. 序列化/反序列化逻辑：检查代码库中是否有依赖于 ID 特定类型或大小的序列化或反序列化逻辑。

3. 第三方库或依赖项：确认是否有与 ID 字段交互的第三方库或依赖项可能会受到 BigInt 更改的影响。

4. 数据库迁移脚本：查看是否有数据库迁移脚本或文档，概述了将 ID 列类型从 int 更改为 BigInt 的过程。

5. 单元或集成测试：检查是否有专门测试 ID 字段的单元或集成测试，如果有，可能需要更新以支持 BigInt。

6. 配置文件或设置：确认应用是否有任何配置文件或设置指定了 ID 字段的数据类型。

7. 数据库触发器或存储过程：检查是否有与 ID 字段交互的数据库触发器或存储过程可能会受到 BigInt 更改的影响。

这些方面都需要仔细检查和测试，以确保更改不会引入新的问题。

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[TerryLam2010]

id 使用的都是long类型。支持bigint

[stale]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically closed because it has not had activity in the last 7 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted". Thank you for your contributions.

[stale]

This issue has been automatically closed because it has not had activity in the last 7 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted". Thank you for your contributions.