Helma Logo
main list history

Version 2 by hannes on 08. October 2007, 14:16

2* Helma does quite a bit of guesswork to determine the child-parent relationship in methods like Node.add* add\* and Node.set*set\*. This is the cause for *bug 543|http://helma.org/bugs/show_bug.cgi?id=543*.

Version 1 by hannes on 08. October 2007, 14:15

1* Not possible to define collections of mountpoints in _parent because it only accepts a two element path
2* Helma does quite a bit of guesswork to determine the child-parent relationship in methods like Node.add* and Node.set*. This is the cause for *bug 543|http://helma.org/bugs/show_bug.cgi?id=543*.
3* There are some places where helma doesn't distinguish between embedded and relational db. One example is *bug 554|http://helma.org/bugs/show_bug.cgi?id=554*, which is caused by Helma marking clean or deleted nodes as modified before adding them to a subnode relation.
3Possible solutions - we need to decide whether the target is Helma 1.6.1 or 1.7.0:
4
5* Add third segment to _parent info for collections of mountpoints
6* Add optional getParentElement() callback that works similar to getChildElement()
7
8
9* Either remove the parent guessing code, or limit it to cases where no _parent has been specified.
10* Do not mark nodes as modified because they're added to a transient node.