Patrick Skillen 74dc3b5b27 Fix query fields being loaded as decimal instead of int
With some DB backends (specifically AWS Postgres RDS) these fields would load as BigDecimal instead of int. This led to
1) versions being displayed as "1.0.2.0" instead of "1.2", and 2) versions with letters (e.g A.0) leading to a 500 error, as BigDecimal#chr doesn't exist
2021-05-06 14:33:16 +01:00
..
2021-02-03 11:59:02 +01:00
2021-02-03 11:59:02 +01:00
2021-02-03 11:59:02 +01:00
2021-03-17 10:31:06 +01:00
2021-02-03 11:59:02 +01:00
2021-02-03 11:59:02 +01:00
2021-02-03 11:59:02 +01:00
2021-02-03 11:59:02 +01:00
2021-02-03 11:59:02 +01:00
2021-02-03 11:59:02 +01:00
2021-02-03 11:59:02 +01:00
2021-02-03 11:59:02 +01:00
2021-02-03 11:59:02 +01:00
2021-02-03 11:59:02 +01:00
2021-02-23 12:49:42 +01:00