BIND 10 #1807: support NSEC for empty non-terminal in in-memory (2/2)

[BIND 10 Development]

#1807: support NSEC for empty non-terminal in in-memory (2/2)
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  jelte
  jinmei                             |                Status:  closed
                       Type:  task   |             Milestone:
                   Priority:         |  Sprint-20120515
  medium                             |            Resolution:  complete
                  Component:  data   |             Sensitive:  0
  source                             |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  3
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:  in-    |
  memory NSEC                        |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by jelte):

 * status:  reviewing => closed
 * resolution:   => complete


Comment:

 I meant fragile in the sense that if you add a record that conflicts with
 another one, masterLoad() rejects it, the callback is not called, and the
 tests continue, but with null pointers in the _rr_XXX members. This caused
 me a few hours of pain yesterday (since I didn't really expect records
 that conflicted but were not actually added to cause a problem).

 Anyway, that's something to address later, this has been merged, and I am
 closing the ticket :)

-- 
Ticket URL: <http://bind10.isc.org/ticket/1807#comment:13>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development