Created on 2014-09-24.17:56:29 by ced, last changed 57 months ago by ced.
For the dynamic states, I think we could enforce the same way but if we use a method on ModelStorage that allow override the behaviour to skip some fields.
With the changeset a382ef9185e7, it is now possible to enforce the readonly attribute on field by preventing to set it as values of create or write just like for ModelFieldAccess when _check_access is set. We should also try to do the same for dynamic states.
|2018-04-05 12:09:44||ced||link||issue3158 superseder|
|2018-03-23 18:33:03||ced||link||issue7257 superseder|
|2017-05-26 12:46:42||ced||link||issue6527 superseder|
|2016-12-28 10:11:47||ced||set||status: unread -> chatting|
messages: + msg31008
|2014-09-24 18:02:05||pokoli||set||nosy: + pokoli|
Showing 10 items. Show all history (warning: this could be VERY long)