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

Cannot view or set bigint max value in console #3667

Closed
dminkovsky opened this issue Jan 8, 2020 · 0 comments · Fixed by #4775
Closed

Cannot view or set bigint max value in console #3667

dminkovsky opened this issue Jan 8, 2020 · 0 comments · Fixed by #4775
Assignees
@soorajshankar
Labels
c/console Related to console k/bug Something isn't working p/high candidate for being included in the upcoming sprint

Comments

@dminkovsky
Copy link
Contributor

I have a row with a bigint value of 9223372036854775807 ("max_bigint"). When I view the row in the console, the value displays as 9223372036854776000. When I try use the console to set the value to max_bigint, I get the following error:

Edit failed!
Int64 is either floating or will cause over or underflow: 9.223372036854776e18
@dminkovsky dminkovsky changed the title Cannot view or set bigint to max value Cannot view or set bigint max value in console Jan 8, 2020
@0x777 0x777 added the c/console Related to console label Jan 9, 2020
@rikinsk rikinsk added k/bug Something isn't working p/high candidate for being included in the upcoming sprint labels Jan 14, 2020
@rikinsk rikinsk removed their assignment Jan 14, 2020
@rikinsk rikinsk mentioned this issue Jan 31, 2020
Closed
@beerose beerose self-assigned this Feb 5, 2020
@Carleslc Carleslc mentioned this issue Apr 26, 2020
Closed
@coco98 coco98 mentioned this issue Apr 29, 2020
Open
14 tasks
@rikinsk rikinsk assigned soorajshankar and unassigned beerose May 14, 2020
@soorajshankar soorajshankar mentioned this issue May 15, 2020
Merged
34 tasks
soorajshankar added a commit to soorajshankar/graphql-engine that referenced this issue May 21, 2020
@soorajshankar
removed parse check for bigint and int
e85c17e 
> while inserting big int from console, int will be sent as string
hasura#3667
rikinsk pushed a commit that referenced this issue May 29, 2020
@soorajshankar
console: allow entering big int values (close #3667) (#4775)
d2aac37
stevefan1999-personal pushed a commit to stevefan1999-personal/graphql-engine that referenced this issue Sep 12, 2020
@soorajshankar @stevefan1999-personal
console: allow entering big int values (close hasura#3667) (hasura#4775)
8a0f576
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@soorajshankar soorajshankar

Labels
c/console Related to console k/bug Something isn't working p/high candidate for being included in the upcoming sprint
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

console: allow entering big int values in the console soorajshankar/graphql-engine
5 participants
@dminkovsky @0x777 @soorajshankar @beerose @rikinsk