When adding a new property that has a defaultValue (or setting it to null when no defaultValue is set) to an existing model instance and then saving it (so it's an update, not a create), the value is not written to the DB.
This causes issues with indexing down the line, at the very least.
As a temporary workaround, one needs to add a migration that first sets the value to a non-default on all existing instances and then sets the default again.
When adding a new property that has a defaultValue (or setting it to null when no defaultValue is set) to an existing model instance and then saving it (so it's an update, not a create), the value is not written to the DB.
This causes issues with indexing down the line, at the very least.
As a temporary workaround, one needs to add a migration that first sets the value to a non-default on all existing instances and then sets the default again.