Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Float from indexer is returned as numeric field #187

Open
moose-code opened this issue Sep 9, 2024 · 3 comments
Open

Float from indexer is returned as numeric field #187

moose-code opened this issue Sep 9, 2024 · 3 comments
Assignees
@JonoPrest
Labels
Bug Something isn't working P4 (Low Priority) Address within sprint

Comments

@moose-code
Copy link
Contributor

Screenshot 2024-09-09 at 16 50 41
Screenshot 2024-09-09 at 16 51 05
@moose-code moose-code added the Triage Determining Scope and Labels label Sep 9, 2024
@JonoPrest
Copy link
Collaborator

Lets investigate if we can configure Hasura to use our own scalar definitions.

@JonoPrest JonoPrest added Bug Something isn't working P4 (Low Priority) Address within sprint and removed Triage Determining Scope and Labels labels Sep 11, 2024
@JonoPrest JonoPrest self-assigned this Sep 11, 2024
@moose-code
Copy link
Contributor Author

Tagging you here @Simon0x so you can track

@JonoPrest
Copy link
Collaborator

@Simon0x to answer the question why is it returned as a numeric. This is because Javascript floats will exceed the size limit of postgres floats. So we use numeric to store them. But we do have BigDecimal now so maybe if we bump into those issues we can just point people to using BigDecimal

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JonoPrest JonoPrest

Labels
Bug Something isn't working P4 (Low Priority) Address within sprint
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@moose-code @JonoPrest