BIND 10 #1845: SQLite3Update.rollbackFailure test fails

[BIND 10 Development]

#1845: SQLite3Update.rollbackFailure test fails
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  jinmei
  vorner                             |                Status:  reviewing
                       Type:         |             Milestone:
  defect                             |  Sprint-20120417
                   Priority:  very   |            Resolution:
  high                               |             Sensitive:  0
                  Component:  data   |           Sub-Project:  DNS
  source                             |  Estimated Difficulty:  4
                   Keywords:         |           Total Hours:  0.1
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:11 jelte]:
 > Hmm, good point, and come to think of it, we should probably also check
 how the 'running transaction' behaves when there is a rollback (the change
 being that the rollback no longer fails, but the next action will with an
 ABORT message). So I also added a check for (no) throw on
 iterator->getNext().

 The code looks okay to me.  But the sqlite3 version on my dev
 environment is still old so I cannot confirm the behavior.  If you
 actually checked the new behavior after ROLLBACK, please merge.  If
 your version is also old...hmm, maybe we should merge it and check the
 behavior on the buildbot that triggered this.

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