BIND 10 #1861: SQLite3 DB creation code should be consolidated

BIND 10 Development do-not-reply at isc.org
Mon Jan 7 19:03:32 UTC 2013


#1861: SQLite3 DB creation code should be consolidated
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  medium        |                    Milestone:  Next-
           Component:  data source   |  Sprint-Proposed
            Keywords:                |                   Resolution:
           Sensitive:  0             |                 CVSS Scoring:
         Sub-Project:  DNS           |              Defect Severity:  N/A
Estimated Difficulty:  5             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by jinmei):

 * milestone:   => Next-Sprint-Proposed


Comment:

 See #2610.  I think it's time to work on this.  It will be followed by
 an update to b10-loadzone so it uses the consolidated separate module
 for DB creation.

 I also suggest the top level interface of the DB creation is DB-type
 agnostic: it would take a unified form of parameter that specifies the
 type of DB, and performs DB-specific initialization internally, maybe
 dispatching the task to a separate module specific to that type of DB.

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


More information about the bind10-tickets mailing list