text: - 18 Apr, 2012 8 commits
  They were originally planned to be enabled with the completion of this branch, but I forgot to enable them before review. As expected, they just passed for SQLite3, too.
  As suggested in review. This will make the caller code simpler. It's also safer in that the caller doesn't have to manipulate the statement separetely (in the previous way StatementProcessor and the caller could use different statements). Also made naming more consistent: in the very initial version the class was called "Executer" and then renamed to Processor. Some variables of this class were still named "exec", etc, but it's more consistent if they are named like "proc".
  this was intended to be a temporary workaround while developing writability, and should have been cleaned up in #1746. no one uses this anymore, so we can safely remove it.
  - the test zone DB was updated by hand with an NSEC3 record in the nsec3 table. - changes to transfer.py was the same one as that in quering.py to support IPv6 transport
  this is a kind of intermediate hack, and we should revisit this point at the level of API/schema design.
  - 17 Apr, 2012 11 commits
  this is a fix to the similar bug as the one fixed in the previous commit, but for the rollback case.
  the test for this uncovered one old regression: accessor cannot be reused for multiple updates. it was fixed in this commit, too.
  defined a new statement for updating the nsec3 table, and used it from addNSEC3RecordToZone. some validation checks are still missing. also made simple cleanup of removing unnecessary namespace qualifiers.
  defining const values in a shared header file isn't illegal, but it could cause definition bloat (it's up to the linker implementation whether to combine them). in practice this probably doesn't matter much for this limited scope purpose, but it's still cleaner to avoid the bloat.
  It gets (re)created on tests, and does not need to be in the repository
  previous commit had a mangled tab due to a copy-paste error from the original diff
  So that the sqlite3_ds.so is found correctly This has been acked on jabber, and is tentatively waiting full resolution in ticket #1895
  As part of conflict resolution, I've extended the unified textToRRset so it takes an optional 'origin' parameter. It's necessary to convert SOA RRs.
  - 16 Apr, 2012 9 commits
  so it will be clearer that they are used only for NSEC3-related records. as suggested in review.
  (as suggested in review)
  the previous "TODO" comment was a leftover when I moved it from the datasrc test. also moved the callback function to the unnamed namespace as it doesn't have to be referrable from others.
  the server components now need to be specified explicitly.
  Conflicts: src/lib/datasrc/tests/memory_datasrc_unittest.cc
  - 15 Apr, 2012 12 commits