Database Studio Table thinks my Postgres bigint column is a string
I have a Postgres database with tables that use bigint colums for IDs. Using these tables in scripts and AgGrids works fine, but the Database Studio Table for some reason seems to interpret them as strings (even though the column config looks like it is correctly identified as bigint.)
As a result, when ordering rows by ID, they are ordered lexographically (eg
1, 10, 11, 2, 20, ...).
Postgres integration seems to work well everywhere else. Also, Database Studio Table doesn't seem to have this problem with MySQL tables.
Anyone have an idea why this is happening?2 Replies