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

[BIND 10 Development]

#1861: SQLite3 DB creation code should be conslidated
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  medium        |                    Milestone:  Next-
           Component:  data source   |  Sprint-Proposed
           Sensitive:  0             |                     Keywords:
         Sub-Project:  DNS           |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 With the introduction of b10-dbutil, we now have 4 places that create
 initial DB file for the SQLite3 data source:
 - isc.datasrc.sqlite3_ds Python module (used by b10-loadzone)
 - two places in C++ libdatasrc (old and new APIs)
 - b10-dbutil (although, technically, it only does 'upgrade' rather than
 'create')

 This is obviously bad.  Although some of the above will be retired
 (hopefully) soon, we should basically maintain the DB schema only in a
 single place.

 My suggestion is to introduce a python module that defines the latest
 SQLite3 schema, and have dbutil use it.  b10-dbutil wold also have a
 "create" option, and on 'make install' we not only check compatibility
 but also create a new one if the DB file doesn't exist.

 After that, remove the DB creation code from libdatasrc.

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