During investigation of
SONAR-12251, we found out that using TYPES.DECIMAL to set a null into a double column in a prepared statement was causing a significant performance hit on SQL Server during DB migration performing massive inserts.
The fix for that was to use TYPES.DOUBLE instead. The fix was applied only to SQL Server.
Given that TYPES.DOUBLE is used in (to be confirmed) all mapping defined in MyBatis (ie. for all DB operations at runtime but for DB migrations), it seems safe to change the type for all SGDBs.
This ticket is about:
- doing the change for all supported SGBDs
- verify Types.DOUBLE is used every where needed in MyBatis mappings