-
Notifications
You must be signed in to change notification settings - Fork 142
Description
Describe the bug
I have the number 76561198859657398 stored as bigint in my database. When I use a select query to get the rows with this number, it shows up as 76561198859657390, the last digit is different. Although it shows a different value, when I use a select query using this different value, there are no rows returned. If I use the original, correct value, rows are returned. This means only the value shown to the user is incorrect, but in the db, the correct value is stored.
To Reproduce
- Create a table with a column of type bigint
- Insert the number 76561198859657398 into this table
- Run a select query to see the value the client will show (It will show the same number except for the last digit, which becomes 0)
Expected behavior
The client should show the correct value, 76561198859657398
Application:
- App client: Antares
- App version: 0.7.35
- Installation source: Github releases
Environment (please complete the following information):
- OS name: Windows 11
- OS version: 24H2
- DB name: Sqlite
- DB version: 3.45.3
Additional context
This value was inserted into the db through python's sqlite3 module. However, when i tried to insert it using queries through the antares client, the same bug happens. I have also tried to insert other numbers, offsetting the original value by 1 each time. The values ...88 through ...99 all show up as the incorrect value I have written above. As for ...70, it shows up as ...80.