[GH-ISSUE #206] Type error: MYSQL, Can't serialize value / Expected type Int but was Long #56

New issue

Closed

opened 2026-03-07 20:44:16 +03:00 by kerem · 3 comments

kerem commented

2026-03-07 20:44:16 +03:00

Owner

Originally created by @Rivi-IT on GitHub (Nov 5, 2020).
Original GitHub issue: https://github.com/dbeaver/cloudbeaver/issues/206

Originally assigned to: @serge-rider on GitHub.

Describe the bug
We are looking for a cloud based SQL Management Tool - so we take a first look at Cloudbeaver.
The installation is container based with podman.

System OS = CentOS 8 minimal
DBM System is MariaDB 10.x
Database is the WordPress database.

To Reproduce
Login to CloudBeaver as Admin or User
Connection to SQL Server as root or User with grant all for WordPress database
DB Admin with grant all for database <db_name>.
Select table "wp_options", try to open table "wp_options".

Error
Can't serialize value (/readDataFromContainer/results[0]/resultSet/columns[2]/maxLength) : Expected type 'Int' but was 'Long'.

Screenshots

Desktop (please complete the following information):

OS: Win 10
Browser: Firefox
Version: 82
Browser: Vivaldi
Version: 3.3.2022
OS: Lubuntu 20.04
Browser: Firefox
Version: 82

Additional context

Originally created by @Rivi-IT on GitHub (Nov 5, 2020). Original GitHub issue: https://github.com/dbeaver/cloudbeaver/issues/206 Originally assigned to: @serge-rider on GitHub. **Describe the bug** We are looking for a cloud based SQL Management Tool - so we take a first look at Cloudbeaver. The installation is container based with podman. - System OS = CentOS 8 minimal - DBM System is MariaDB 10.x - Database is the WordPress database. **To Reproduce** Login to CloudBeaver as Admin or User Connection to SQL Server as root or User with grant all for WordPress database DB Admin with grant all for database <db_name>. Select table "wp_options", try to open table "wp_options". **Error** Can't serialize value (/readDataFromContainer/results[0]/resultSet/columns[2]/maxLength) : Expected type 'Int' but was 'Long'. **Screenshots** ![CloudBeaver-Error-BigInt](https://user-images.githubusercontent.com/67333044/98264126-e05a6a80-1f87-11eb-9bbb-97a8fa90853e.PNG) ![CloudBeaver-Error-Fields](https://user-images.githubusercontent.com/67333044/98264045-c9b41380-1f87-11eb-89bd-06884af2a0dc.PNG) **Desktop (please complete the following information):** - OS: Win 10 - Browser: Firefox - Version: 82 - Browser: Vivaldi - Version: 3.3.2022 - OS: Lubuntu 20.04 - Browser: Firefox - Version: 82 **Additional context**

kerem closed this issue

2026-03-07 20:44:16 +03:00

kerem commented

2026-03-07 20:44:17 +03:00

Author

Owner

@kseniiaguzeeva commented on GitHub (Nov 6, 2020):

Thank you for the bug report.

@kseniiaguzeeva commented on GitHub (Nov 6, 2020): Thank you for the bug report.

kerem commented

2026-03-07 20:44:17 +03:00

Author

Owner

@serge-rider commented on GitHub (Nov 6, 2020):

Fixed.
GraphQL (java-graphql library) doesn't allow Int values bigger than maximum 32bit signed integer.
Also JS and GraphQL don't support 64 bit integers (as JS represents all numbers as double precision float values).

I've changed GQL data types from Int to Float in metadata describing data types. It fixed this particular issue.

However we may have other problems with 64 bit long integers in future.

@serge-rider commented on GitHub (Nov 6, 2020): Fixed. GraphQL (java-graphql library) doesn't allow Int values bigger than maximum 32bit signed integer. Also JS and GraphQL don't support 64 bit integers (as JS represents all numbers as double precision float values). I've changed GQL data types from Int to Float in metadata describing data types. It fixed this particular issue. However we may have other problems with 64 bit long integers in future.

kerem commented

2026-03-07 20:44:17 +03:00

Author

Owner

@Rivi-IT commented on GitHub (Nov 8, 2020):

Thanks for fix: table rows are fetched and displayed, row update is working too.
However, i didn't check all features till now .

@Rivi-IT commented on GitHub (Nov 8, 2020): Thanks for fix: table rows are fetched and displayed, row update is working too. However, i didn't check all features till now <g>.

kerem referenced this issue

2026-03-07 21:03:53 +03:00

[PR #56] [MERGED] feat(administration): administration item #1413