You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When saving an empty string, I don't expect it to be converted to nil. That is not normal behaviour. This breaks database NOT NULL string fields.
Probably caused by 9e528f1. I think that should be a configurable option, not a hard-coded behaviour.
Applications with schemas so badly defined that they actually need to map the empty string to NULL in string fields should have to configure that specially.
The text was updated successfully, but these errors were encountered:
inopinatus
changed the title
bug: saving an empty string converts to nil, triggered NOT NULL violation.
Saving an empty string converts to nil, triggered NOT NULL violation.
Jul 24, 2019
When saving an empty string, I don't expect it to be converted to nil. That is not normal behaviour. This breaks database NOT NULL string fields.
Probably caused by 9e528f1. I think that should be a configurable option, not a hard-coded behaviour.
Applications with schemas so badly defined that they actually need to map the empty string to NULL in string fields should have to configure that specially.
The text was updated successfully, but these errors were encountered: