Enforce bigint for all int fields derived from JSON instead of doing more...
Enforce bigint for all int fields derived from JSON instead of doing more complete refactor (#24494) Pursuant to #22732. Should basically eliminate it with prejudice by saying that any int should fit bigints in our point of view in postgres.
Showing
- src/metabase/driver/sql_jdbc/sync/describe_table.clj 1 addition, 1 deletionsrc/metabase/driver/sql_jdbc/sync/describe_table.clj
- test/metabase/driver/mysql_test.clj 9 additions, 9 deletionstest/metabase/driver/mysql_test.clj
- test/metabase/driver/postgres_test.clj 9 additions, 9 deletionstest/metabase/driver/postgres_test.clj
Loading
Please register or sign in to comment