Values are currently stored with a limited number of digits allowed after the decimal place*, so values with higher precision are rounded when they're saved to the database. Running the same import again prompts an overwrite of the records that have been added, since the rounded values (e.g. 91.489362) don't always match the provided values (e.g. 91.4893617). This doesn't cause any problems, but could be confusing to an operator of the data import process.
- This appears to be six, but the table structure says
decimal(19,9), so it should theoretically be nine.
Values are currently stored with a limited number of digits allowed after the decimal place*, so values with higher precision are rounded when they're saved to the database. Running the same import again prompts an overwrite of the records that have been added, since the rounded values (e.g. 91.489362) don't always match the provided values (e.g. 91.4893617). This doesn't cause any problems, but could be confusing to an operator of the data import process.
decimal(19,9), so it should theoretically be nine.