This repository has been archived by the owner on Nov 10, 2023. It is now read-only.
Use int64 (bigint) data type for date time #12
Merged
Conversation
This file contains 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
Change database schema (Prisma schema)
DateTimedata type toBigIntorint 64What
Change database schema that matches with gRPC proto
Why
If we use
DateTimein the database schema, we will have a type that refers to the DateTime fields generated from Prisma. And have a duplicated one in gRPC api-types package that usesint64ornumberin TS type.How
We just change the database datetime-related fields to bigint as same as gRPC proto
Todo list (if applicable)
Checklist