Closed Sanpele closed 2 years ago
This may be because of poor planning writing the sql creating the table. the sql was :
prov_rate DECIMAL(2,1) NOT NULL
However this only includes 2 digits, one before and one after the decimal -> . with numbers like 48.3 i wonder if its just defaulting to largest possible, which would be a slightly weird default as it makes debugging hard. Likewise the only way to investigate is to either delete and remake the table, or use another table.
Going with option 2 i believe.
when printing rate from the DB, they always appear as 9.9. However the initial covidDataObj's values being updated correctly. Therefore somewhere in the DB implementation the values are getting