Opened 8 years ago

Closed 6 years ago

#1861 closed defect (wontfix)

SQLite3 DB creation code should be consolidated

Reported by: jinmei Owned by:
Priority: medium Milestone: Remaining BIND10 tickets
Component: data source Version: bind10-old
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DNS Feature Depending on Ticket:
Estimated Difficulty: 5 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no


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.


Change History (5)

comment:1 Changed 8 years ago by jinmei

  • Summary changed from SQLite3 DB creation code should be conslidated to SQLite3 DB creation code should be consolidated

comment:2 Changed 8 years ago by jelte

  • Milestone Next-Sprint-Proposed deleted

comment:3 Changed 7 years ago by jinmei

  • Milestone set to Next-Sprint-Proposed

comment:4 Changed 6 years ago by tomek

  • Milestone set to Remaining BIND10 tickets

comment:5 Changed 6 years ago by tomek

  • Resolution set to wontfix
  • Status changed from new to closed
  • Version set to old-bind10

This issue is related to bind10 code that is no longer part of Kea.

If you are interested in BIND10/Bundy framework or its DNS components,
please check

Closing ticket.

Note: See TracTickets for help on using tickets.