new_node: Do not reuse old pointers in zone copy.
- node->new_node is thus obosolete. - since hattrie_dup made almost a full copy anyway, it's feasible to let the zone contents recreate the zone anew, with proper pointers. (new node was used to set only parent pointer, others were reset anyway in adjusting, all this will die in the new zone API, but at least like this it's easier to maintain.)
Showing
- src/common/hattrie/hat-trie.c 4 additions, 0 deletionssrc/common/hattrie/hat-trie.c
- src/knot/nameserver/update.c 10 additions, 10 deletionssrc/knot/nameserver/update.c
- src/knot/server/zones.c 3 additions, 4 deletionssrc/knot/server/zones.c
- src/knot/updates/xfr-in.c 14 additions, 105 deletionssrc/knot/updates/xfr-in.c
- src/knot/updates/xfr-in.h 2 additions, 4 deletionssrc/knot/updates/xfr-in.h
- src/knot/zone/node.c 8 additions, 62 deletionssrc/knot/zone/node.c
- src/knot/zone/node.h 0 additions, 10 deletionssrc/knot/zone/node.h
- src/knot/zone/zone-contents.c 112 additions, 31 deletionssrc/knot/zone/zone-contents.c
- src/knot/zone/zone-tree.c 0 additions, 53 deletionssrc/knot/zone/zone-tree.c
- src/knot/zone/zone-tree.h 0 additions, 19 deletionssrc/knot/zone/zone-tree.h
- src/libknot/rr.c 1 addition, 1 deletionsrc/libknot/rr.c
Please register or sign in to comment