Pierre van Rooden <[EMAIL PROTECTED]> wrote: > I think an unset field should possible return 'null' with getValue() > even if it is marked as NOT NULL. Or perhaps it should throw an > exception. The method getNodeValue() should also do this, as there is no > 'empty node' value. > Returning null for a field that cannot be NULL may be strange, but in > the case of a (new) node being editted on, this can happen.
It migh be the case that this can happen, but I would like to consider it a bug, because I think it would violate my rule that it should not matter if a node is new or not. I think 'unset' fields are silently translated to empty values by the storage layer now, if those fields are null, and are therefore indistinguishable from really empty fields. I think it should then also be valid before committing the node to the database. Michiel -- Michiel Meeuwissen Mediacentrum 140 H'sum +31 (0)35 6772979 nl_NL eo_XX en_US mihxil' [] ()
