No. The only thing is that an mmbase restriction has a flag
'always/oncreate/onchange/never', which main goal was e.g. to avoid
problems with a restriction like 'field value > now', which is a nice one
during creation of the node, but when you save it again on a later time,
the field value may have become smaller then 'now', so you don't want to
enforce the restriction then.
I still feel that a basetype should not have any restriction, even
'soft' ones, other than that the data entered is compatible for its type.
Sub-type should be stricter than the base type, not looser.
_______________________________________________
Developers mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/developers
