Repository navigation
Unable to set null to field #2344
Description
Activity
Right this is an historical decision that was taken a while ago but that I'd like to change at some point. When you set the field to None, it is removed from the document instead of being actually set to None.
I guess it was done to save a bit of space in MongoDB but I think it was a bad design decision and I'd like to change that in a near future.
Reacted by Cesar Charria, Ryan Kroon and Natanael RussoTo add to this, I feel like if the Field has
null=Falseand does not have a default value, then the default value should be the "zero value" of that type.
for example:
StringField defaults to ""
IntField defaults to 0
BooleanField defaults to False
etcHello, des someone has an Ide how to fix it? using pymongo directly is for sure an option, but for me it would mean to rewrite a bunch of code. Ideally, I would like to have something like: if null=True for a field is set and None is provided as value, save it with the mongodb "null", otherwise skip.
I created a document A.
A.field1= None
A.save().
But when I try to save the document to MongoDB, the keys with a "None" value are not inserted into the collection. The field1 disappear.