Closed chinalu closed 2 years ago
Describe the bug Same as #12773, when field type is Decimal or Float。
Decimal
Float
If old value in database is 1.0, then use RawValue to update this field, will reproduce this bug. Because of following logic
case Column::TYPE_DECIMAL: case Column::TYPE_FLOAT: let changed = floatval(snapshotValue) !== floatval(value); break;
Because:
floatval(new \Phalcon\Db\RawValue("f+1")) === float(1)
So to reproduce the issue, should be
Resolved in https://github.com/phalcon/cphalcon/pull/15781
Describe the bug Same as #12773, when field type is
Decimal
orFloat
。If old value in database is 1.0, then use RawValue to update this field, will reproduce this bug. Because of following logic
Because:
So to reproduce the issue, should be