Use default property values when adding a new column in a migration

[segiddins]

No description provided.

[porsager]

This one bit me as well. Is there any timeframe on this or would it maybe be an idea to note it in the migration documentation?

[jpsim]

I just added this to our docs: https://realm.io/docs/objc/latest/#migrations

Note that default property values aren't applied to new objects during migrations. We consider this to be a bug and are tracking it as #1793.

[rsahara]

I hope this will be fixed soon as it's difficult for the developers to test if the migrated DB works for each of the previous versions of the realm. (after 90 updates in our case)

We recently received errors because of unexpected null string properties (with normally a default value of @""), when we released a major update of our app.

[jpsim]

The challenge here is to only ever set default values if they haven't explicitly been set by a user, which in turn requires tracking which setters were invoked.

[JadenGeller]

This does seem challenging. I would imagine if a user explicitly set a properties value back to the default, it should not be automatically migrated if the default changes. It almost seems that there ought to be some sort of resetProperty: method.

EDIT: I just realized that this issue only pertains to new columns, which simplifies it.

[JadenGeller]

@jpsim Couldn't we also strictly set the default values before the user sets the property?

[jpsim]

Yes, I think eagerly setting default values before user set the property would be acceptable. It shouldn't have a significant performance impact, but I'd prefer if we checked nonetheless.

[jemshit]

So what is solution for assigning default value for new Column after migration ? any magical method ?

[werediver]

No magic. Set manually :(

[mrgcohen]

setting manually (reference)
https://realm.io/docs/swift/latest/#updating-values

[guhan0]

Any solution or fix to this issue?

[ThreadPitt]

Still happens here, any progress on this?
Please, pretty PLEASE :-)