This is because MySQL doesn't support storing of NaN valuels, and therefore go-mysql-server isn't going to either. Float fields/columns are always mapped to be nullable now, otherwise we would have to replace NaN/Inf with 0.
This is because MySQL doesn't support storing of NaN valuels, and therefore go-mysql-server isn't going to either. Float fields/columns are always mapped to be nullable now, otherwise we would have to replace NaN/Inf with 0.