mongoDB: is it better to remove a field to nullify it?

Asked May 30 '18 at 19:08

Active May 31 '18 at 12:59

Viewed 64 times

I would like to know which is better for an existing document: To remove a field to nullify it, or to keep the field and simply set it to null?

I'd also like to know more about the process of saving the document: Will the document be saved in the same place or will an entirely new document be saved somewhere else on the disk?

Note: This question has absolutely nothing in common with "Is shortening MongoDB property names worthwhile?"! I'm asking about saving a record that already exists by removing a field instead of nullifying it.

edited May 31 '18 at 10:24

Kjartan

18,591
15
71
96

asked May 30 '18 at 19:08

zeus

12,173
9
63
184

Will any of your queries be filtering on if this field is present? – Adam Harrison May 30 '18 at 23:43
yes, but i can do simply myField:Null and it's will also take in account not existing field .. – zeus Jun 03 '18 at 09:29

mongoDB: is it better to remove a field to nullify it?

0 Answers0