BIND 10 #1756: revise "ITERATE" query in sqlite3_accessor

[BIND 10 Development]

#1756: revise "ITERATE" query in sqlite3_accessor
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:  muks
                Type:  defect        |                       Status:
            Priority:  medium        |  assigned
           Component:  data source   |                    Milestone:
            Keywords:                |                   Resolution:
           Sensitive:  0             |                 CVSS Scoring:
         Sub-Project:  DNS           |              Defect Severity:  N/A
Estimated Difficulty:  6             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by jinmei):

 See the discussion around this:
 https://lists.isc.org/pipermail/bind10-dev/2013-January/004204.html

 I guess it's time to complete this task with *adopting* it.

 If our basic expectation is to not use SQLite3 for huge zones,
 this change won't particularly help but won't do harm either
 (because the additional overhead would also be marginal).

 If the user still wants to use SQLite3 with understanding the basic
 expectation and do it at their own risk, it helps them.  And the
 additional overhead is part of the cost they need to pay in that case.

 So, either way, it doesn't harm and help some cases.  Since we
 basically completed the task itself, all we have to do is to just
 merge it.

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