Skip to content
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

Setting fields empty stores empty strings rather than NULL values #4369

jremmurd opened this issue May 14, 2019 · 0 comments


None yet
1 participant
Copy link

commented May 14, 2019

Bug Report

Empty fields in data objects are stored as empty strings inside the object_store table which results in errors/unexpected behaviour when using unique keys especially when using dataobject inheritence.

As a result you cannot set an empty value in more than one object in a unique field and save the object (because these are empty strings ''). But you can create an arbitrary amount of objects (because those newly created objects have NULLvalues). This behaviour makes it very difficult to change any unique field's value, especially when using inheritence where you are depent on being able to set empty values.

This is related to #4333.


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.