adding a new enum sets historical data

[jamie]

when i create a new enum it will set all records to the default, every single one of them. it should just set it as null

[victor]

You just need to add an empty Option and make it Default (this is how it always worked).

[jamie]

You just need to add an empty Option and make it Default (this is how it always worked).

ahh some undocumented hack, perhaps its time to update documentation or maybe don't automatically set historical data?

[yuri]

The default value is set as DB default for all fields with scalar values. It's how it works. There are pros and cons in it. I'd rather keep it as it is.

[yuri]

https://github.com/espocrm/documentation/commit/661cb37d9e22f77e71a8e292f28a70de326399ba

[jamie]

The default value is set as DB default for all fields with scalar values. It's how it works. There are pros and cons in it. I'd rather keep it as it is.

setting historical data a major con, and the fact that it isn't documented is also another con, if your going to make non standard behavior you should at least document it, though the best would be a check box to toggle the behavior

[yuri]

It's how databases have been always working. The default value populates existing records if a null is not allowed. The application does not do it, it's the behavior of the database. Calling it a non-standard behavior is a moot point. It's already added to the docs, no need to re-iterate the same.