We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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
The text was updated successfully, but these errors were encountered:
phalcon#15413 - Fixed Phalcon\Db\RawValue usage bugs in Phalcon\Mvc\M…
e4b6bc8
…odel::doLowUpdate()
phalcon#15413 - Updated CHANGELOG-5.0.md
19e6a92
phalcon#15413 - Fix
14bd22e
Resolved in #15781
Sorry, something went wrong.
BeMySlaveDarlin
Successfully merging a pull request may close this issue.
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
The text was updated successfully, but these errors were encountered: