-
Notifications
You must be signed in to change notification settings - Fork 46
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
Storing boolean value in a non-defined/string field #1065
Comments
The fields are strictly typed and if type is null, Given this fact, the exception seems correct to me. Can we close this issue or why |
Before boolean was stored as "1" (true) or null (false) if stored in string field, now it throws an exception. Shouldn't it store as before? |
Wdym by store? In php, we store it natively - |
Will try to make repro code - I saved a false value to a string field, and got "must not be boolean" as an exception. However, if you save a false boolean value to a string field it should convert it to null, shouldn't it? And true should be saved as 1 in a string field. |
No, it should not, it is a type error. Other people will open an issue |
This then is a BC break, as it was automagically converted before, wasn't it? I like automatic type conversions, but am fine either way. And I don't care if false is converted to "0" or null in a string, all fine. |
Probably some fixed bug :) |
Steps to reproduce:
Result:
Exception Field must not be boolean
Behaviour before = Expected behaviour: Was typecasted to null or 1 automatically.
The text was updated successfully, but these errors were encountered: