Closed NTSFka closed 3 months ago
You're probably right that it can be simplified. I just need to leave the fix for SQL Server, which returns decimal numbers like .123
, making it impossible to cast them using (float)
. 0c2ebef51949391ce21823d8186cf3300c7485f7
Version: 3.2, 3.1.7, 3.1, ...
Bug Description
Row normalizer changes value of floating point value in scientific notation (e.g. 1E-10) with exponent that ends with zeroes. This is only done when PDO driver returns floating point value as
string
(PostgreSQL) and not asfloat
(MySQL and SQLite3).Steps To Reproduce
Can be reproduced by adding this code to
ResultSet.normalizeRow.postgre.phpt
.It fails with:
Database returns value as
'1.2E-10'
but row normalizer changes value to'1.2E-1'
by removing trailing zeroes.Problem is caused by first block of handling float and decimal values (from
v3.2
):Expected Behavior
Floating point values shouldn't be changed.
Possible Solution
1) Remove code that remove trailing zeroes from string representation of floating point values - tests didn't failed. 2) Modify condition in row normalizer to ignore string in scientific notation.
Before 3.1.5 there was code that returns numeric values that are not possible to represent as floating point as string (if I understand correctly) but that was removed in order to fix #289. In result I see no point of having that code because PHP's cast operator can handle conversion and floating point and decimal values are never returned as string after 3.1.5.