I just found another issue when use ValueMixin with required fields on it. Because MultiValueMixin will create the Value record and set only one field at a time, the required constraint will raise an error. I think the right design is to have the default value stored on the Value model and have the MultiValue model calling them. At least for Value model with many required fields (like ConfigurationSaleMethod).
|2017-03-28 20:54:19||ced||set||messageid: <email@example.com>|
|2017-03-28 20:54:19||ced||set||recipients: + yangoon, ohuisman, eric, albertca, smarro, resteve, pokoli, angel, jesteve, guillemNaN, reviewbot, unicode2013|
|2017-03-28 20:54:19||ced||link||issue2349 messages|
Showing 10 items. Show all history (warning: this could be VERY long)