GitLab

Provide separate list of parameter strings for deleting NSEC3 records.
It is cleaner to have separate enum for listing the parameters needed to
delete NSEC3 than re-using generic delete parameters and having the hash
passed twice.

Fix SQLite backend so the deletes are not so slow.

This is the urgent part of the fix; we'll have another half of the branch
later, to clean up some details.

mysql_lease_mgr.

I introduced problem by fixing a typo in a comment in a zone file.
The character positions or file sizes of the file were hardcoded
in the unit test. I had seen the failure on my system but didn't
associate it. (My mistake for not looking closely.)

The typo fix added one character so changed the hardcoded 549 to 500
and 506 to 507.

(Later maybe some macros should be used for this?)

merged

mostly in documentation or in comments

reviewed by muks via jabber

includes output changes for two isc_throw.

Fix failure to connect in msgq tests.

Added braces to a single-line "if" statement.  Also corrected
some comments and removed trailing spaces from some statements.

Describe the value of the column in the NSEC3 case.

Conflicts:
	ChangeLog

and also remove dash before beta revision in version naming

unit tests.

trivial, no review

I wrote this some month ago.
Didn't get reviewed.

No real change, just sorting the messages in the message file.

Provide descriptions for log messages added in the previous commit, the
ones for more detailed logging during update of database based
datasource.

Provide the data being updated and operations on database based
datasources.

Applied verbatim from the mailing list.

For the previous commit, adding the reverse name to the list of
parameters for delete.

This is significantly faster, as the rname has an index on it, while the
name doesn't.

Applied verbatim as sent on the mailing list. Documentation will come
soon.

some compilers claim it causes a copy whie it's defined non copyable,
triggering an error.  this fixes some build failure reported by the bots.
should mostly trivial, so committing at my discretion.

acknowledged on jabber

(used tools/reorder_message_file.py)

instead of the "static" BIND zone.  there's no difference between these two
any more, so this is just a matter of style.