BIND 10 #730: sqlite3 data source could keep locking the DB on exception

[BIND 10 Development]

#730: sqlite3 data source could keep locking the DB on exception
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  jinmei
  jinmei                             |                Status:  assigned
                       Type:         |             Milestone:  New Tasks
  defect                             |            Resolution:
                   Priority:  major  |             Sensitive:  0
                  Component:  data   |           Sub-Project:  DNS
  source                             |  Estimated Difficulty:  0.0
                   Keywords:         |           Total Hours:  0
            Defect Severity:         |
  Medium                             |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by jinmei):

 * milestone:   => New Tasks


Comment:

 Replying to [comment:2 shane]:
 > Jinmei, this is for the old data source model, right?

 Right.  The new version should avoid this problem in a more
 comprehensive and reliable manner.

 > Since this will be resolved (right?) when we move to the new data source
 model, should we resolve it as WONTFIX perhaps?

 To be consistent with what we've done for old-datasrc specific issues,
 yes, probably.  But we should really need to complete the migration if
 we allow that excuse.  (the only remaining stuff except hotspot cache
 is the NSEC3 support, which shouldn't be so difficult as most of the
 difficult part is already in the auth::Query framework).

 Anyway, I'm closing this ticket.

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