Eduard Witteveen <[EMAIL PROTECTED]> wrote:
> Michiel Meeuwissen wrote:
>
> >And even that, with the advent of plugins on get- and set- of bridge cannot
> >is not certain.
> >
> >
> Indeed, but how are we gonna explain all this to the users? Maybe we
> need an isNull(string fieldname)?
I'm not against isNull(fieldName) but I think it has hardly any relation to
this issue. Btw, much more usefull would be NodeManager#isNullable.
I think it is not very hard to explain all this, but lets first define it
to ourselves. What should happen with null and unset values!!
Btw way, I just created some more test-cases in tests/brdige, and discovered
that:
node = cloud.getNodeManager("aa").createNode();
node.setValue("bytefield", null);
node.setValue("doublefield", null);
node.setValue("floatfield", null);
node.setValue("intfield", null);
node.setValue("longfield", null);
node.setValue("stringfield", null);
node.commit();
(EmptiedNodeTest, all test-cases failing, because they suppose that
getValue() should return null).
is different from
node = cloud.getNodeManager("aa").createNode();
node.commit();
(EmptyNodeTest, test-cases currently succeeding becasuse getValue()'s indeed
return null).
I don't think that is desirable.
Michiel
--
Michiel Meeuwissen
Mediacentrum 140 H'sum
+31 (0)35 6772979
nl_NL eo_XX en_US
mihxil'
[] ()
