so that if they have nested default values, which may be set to 'local', and modified later, the original isn't changed. (technically it should be enough to do the copy when setting, but it's safer to copy them entirely for now)
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
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.
Logging output from different processes can get jumbled up if written
to stderr (because messages are output in multiple write(2) operations.)
This change updates the documentation to suggest that the user switch
to stdout if that happens.
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.
It puts the configuration of the zone (which is loaded from SQLite3
database) and the database at the disposition of the test. Then it asks
it to load the zone and it expects it to load it.
The file is created during tests so the original one is not destroyed.
So it makes no sense to store the file that is being modified by the
test each run in git.
