As raised by johnedwardg.pedregosa while testing MDL-75191 (thanks! - this comment contains more context)

Columns containing float values, either natively by their type or when set to Average aggregation, display the value formatted which can result in a loss of precision

However the same column is sorted by it's original DB value, which can lead to inconsistencies in the UI when the user is presented with what appear to be identical column values (e.g. 0.11) but which have different values when stored in the database with more precision (e.g. 0.109 vs. 0.113)