-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
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
[BUG]: Model setters do not call during hydration #14810
Labels
Projects
Comments
Can be related to #14766 |
3 tasks
Zephir issue has been fixed in #2078. I'll release new version ASAP |
Zephir 0.12.18 released: https://github.com/phalcon/zephir/releases/tag/0.12.18 |
zsilbi
added a commit
to zsilbi/cphalcon
that referenced
this issue
Oct 16, 2020
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Questions? Forum: https://phalcon.link/forum or Discord: https://phalcon.link/discord
Describe the bug
During hydration using Resultset::HYDRATE_RECORDS mode Models protected/private property values sets like they are public ones instead to be set using setters.
To Reproduce
Generate any model that uses setters and getters. At setters throw any kind of exception. Retrieving record by calling Model::findFirst() expected that exception will be thown in setters. But there is no any exception is thrown and we have a Model instance with setted values.
Steps to reproduce the behavior:
Also there is another unexpected behaviour. If we override cloneResultMap method and create a new instance of base model and set a value for protected property no exception is thown as expected.
Details
Environment:
OS: Linux UBT 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64
PHP Version: 7.4.2
PHP SAPI: cli
PHP Bin: /usr/bin/php7.4
PHP Extension Dir: /usr/lib/php/20190902
PHP Bin Dir: /usr/bin
Loaded PHP config: /etc/php/7.4/cli/php.ini
Versions:
Phalcon DevTools Version: 4.0.1
Phalcon Version: 4.0.3
AdminLTE Version: 2.3.6
The text was updated successfully, but these errors were encountered: