Relation.getVirtualMapping() now returns the right DbMapping even
for prototyped collection nodes, so no more extra code for this case is needed here.
This commit is contained in:
parent
ff95d49d4a
commit
8112e2a40c
1 changed files with 3 additions and 6 deletions
|
@ -1267,12 +1267,9 @@ public final class NodeManager {
|
||||||
node = (Node) home.createNode (kstr);
|
node = (Node) home.createNode (kstr);
|
||||||
else
|
else
|
||||||
node = new Node (home, kstr, safe, rel.prototype);
|
node = new Node (home, kstr, safe, rel.prototype);
|
||||||
if (rel.prototype != null) {
|
// set prototype and dbmapping on the newly created virtual/collection node
|
||||||
node.setPrototype (rel.prototype);
|
node.setPrototype (rel.prototype);
|
||||||
node.setDbMapping (app.getDbMapping (rel.prototype));
|
node.setDbMapping (rel.getVirtualMapping ());
|
||||||
} else {
|
|
||||||
node.setDbMapping (rel.getVirtualMapping ());
|
|
||||||
}
|
|
||||||
|
|
||||||
} else if (rel != null && rel.groupby != null) {
|
} else if (rel != null && rel.groupby != null) {
|
||||||
node = home.getGroupbySubnode (kstr, false);
|
node = home.getGroupbySubnode (kstr, false);
|
||||||
|
|
Loading…
Add table
Reference in a new issue