BIND 10 #2555: clean up exceptions in sqlite3_accessor

[BIND 10 Development]

#2555: clean up exceptions in sqlite3_accessor
-------------------------------------+-------------------------------------
                   Reporter:  jelte  |                 Owner:
                       Type:  task   |                Status:  new
                   Priority:         |             Milestone:  New Tasks
  medium                             |              Keywords:
                  Component:         |             Sensitive:  0
  Unclassified                       |           Sub-Project:  DNS
               CVSS Scoring:         |  Estimated Difficulty:  0
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
 During #2541, we noticed that the exceptions that are thrown are a tad
 inconsistent; sometimes sqlite3 errors get thrown as SQLite3Error,
 sometimes as DataSourceError, and we should probably use InvalidOperation
 for things like double startTransaction() calls, and calls that expect a
 transaction to be active but are not.

 If these are changed, don't forget to update the python wrapper!

 These might have some unexpected side-effects so please plan to run it
 past the buildbots as well :) (and plan a bit of extra time to fix those)

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