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.
In that case, I suggest something else: that, on creation of node, alle fields that cannot be NULL are intialized to a 'proper' default value (this can be done in the setDefaults method, which is now empty).
This makes data consistent and avoids strange coding at the 'retrieval' side.
-- Pierre van Rooden Mediapark, C 107 tel. +31 (0)35 6772815 "Never summon anything bigger than your head."
