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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(store-sync): fix overflowing column types, bump postgres sync version #2270
fix(store-sync): fix overflowing column types, bump postgres sync version #2270
Changes from all commits
e0e29c1
078f4a5
823d8f7
6f4f2cc
7e5b76e
280e977
da9b921
6a40150
0ce8e4d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can't comment below but does
int48
need to be bumped to the next size up too?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What does that mean sorry? Anyway I don't think so, int48 is already a postgres
bigint
here?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We chatted IRL and we mixed up the JavaScript and Postgres column types.
but maybe
uint64
andint64
need to move down because they may not fit within thebigint
column typeThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@holic it definitely doesn't fit -
uint64
is 8 bytes unsigned, postgresbigint
is 8 bytes signed:https://www.postgresql.org/docs/current/datatype-numeric.html