BIND 10 #2877: slow updates to SQLite3 data source

[BIND 10 Development]

#2877: slow updates to SQLite3 data source
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  defect        |  jinmei
            Priority:  very high     |                       Status:
           Component:  data source   |  reviewing
            Keywords:                |                    Milestone:
           Sensitive:  0             |  Sprint-20130423
         Sub-Project:  DNS           |                   Resolution:
Estimated Difficulty:  3             |                 CVSS Scoring:
         Total Hours:  0             |              Defect Severity:  N/A
                                     |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:11 vorner]:

 > > - I wonder whether we should now make `DeleteRecordParams` non-NSEC3
 > >   records only, just like we separate `AddRecordColumns` and
 > >   `AddNSEC3RecordColumns`.  It's a tradeoff between reducing the
 > >   amount of code and disadvantages of overloading (conceptual
 > >   confusion, need for additional tweak in the accessor side), but at
 > >   this point I guess the latter outweighs the former.  If we keep
 > >   overloading, we'll at least need what's in RNAME for NSEC3 and
 > >   what's accessor should do with it.  I'd also guess we'd rather
 > >   specify an empty string in RNAME for the NSEC3 case.
 >
 > The separation seems to make sense to me. But I think we might want to
 do it in a separate ticket. Would you agree with merging it this way, to
 solve the slow updates, and create a ticket for the cleanup?

 If we both think it makes sense, I'd be inclined to complete it within
 this ticket, as I believe it's basically an easy addition while I
 suspect it would be quite possible that the separate ticket is
 considered less important than others and not adopted in near feature
 or ever.

 So my specific suggestion is to merge the current branch to master,
 keep this ticket open, and complete the cleanup work within this task.

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