-
Notifications
You must be signed in to change notification settings - Fork 485
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
Chore: Make sure sequelize BIGINTs are returned to us as numbers #368
Comments
Is this still relevant? If so, just comment with any updates and we'll leave it open. Otherwise, if there is no further activity, it will be closed. |
Still want to get to this, although not sure how much effort it'll be |
Is this still relevant? If so, just comment with any updates and we'll leave it open. Otherwise, if there is no further activity, it will be closed. |
I feel like this might be related to an intermittent exception we're seeing |
Is this still relevant? If so, just comment with any updates and we'll leave it open. Otherwise, if there is no further activity, it will be closed. |
For the range of numbers we deal with, we should be able to adjust the default behavior of
pg
to return numbers to us for the BIGINT field, as opposed to strings.Relevant links:
The text was updated successfully, but these errors were encountered: