fix(server): 数据库时间字段改用 BigInt 以修复毫秒时间戳溢出 - #1
Open
283375 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
背景
Prisma
Int映射 PostgreSQL INT4, 上限 2^31-1, 装不下毫秒级 Unix 时间戳, 导致投递/岗位写入溢出报错.改动
Int改BigInt, 新增 migration 扩列Number()把 bigint 转回 DTO 的 number 毫秒契约 (bigint 无法过 trpc 默认 JSON 序列化)验证
pnpm check/pnpm lint通过