GitLab

Normal one and wildcard one. Empty-nonterminal is not included here.

That one was getting really hairy and it wouldn't serve it's purpose in
the following work.

Currently it takes set of types we're interested in and returns all of
them, the logic to decide which one to take is left to the caller. This
simplifies the method and doesn't hurt the rest much, as the rest needed
to know what to ask for anyway.

Also, it allows getting NSEC or NSEC3 records in the same database
search almost for free.

dash to underscore

(obvious by looking in spec and python script.)

DB file has write permission.  hopefully it should fix the distcheck failure
on the freebsd8 buildbot.

directly committed and pushed for master.

briefly discussed on jabber, didn't see any objection.

with fixing conflicts in src/lib/datasrc/tests/database_unittest.cc

with fixing conflicts in database_unittest.cc.

RRSIG support for database DataSources

with fixing conflicts.  The conflicts were only in database_unittest.cc,
and the necessary fix is straighforward updates to make newly added tests
work as TYPED_TESTs.

with the mock accessor and sqlite3 accessor.

operations with multiple adds and deletes.

of the in-memory data source client.

of class member variables (which are now removed).  also added a test to
detect a bug in the previous code where the sigtype field for addRRset
was incorrectly carried over after adding an RRSIG.

Also updated doc and tests accordingly.

* Avoid infinite recursion - the operator | kind of happened to call
  itself by accident.
* Re-added lost | dnssec_opt_.

the MockAccessor class definition.

catch exception in rollback explicitly.  added a test case for that.

implementation completely within .cc as even the class name doesn't have to
be visible.

startUpdateZone() to be more consistent with getIterator()).

result value of system() was unused. And if we're catching it anyway, might as well error on it if the command failed.
reviewed on jabber

While backends are allowed to pass DNSSEC data when not asked to, they
don't have to, so we need to ask for it. Test backend therefore doesn't
return the DNSSEC data when not asked to, to check it really asks.

Only positive matches for now.

This looks like someone already prepared for it, it only needs to
passing the intent to few functions and everything handles itself well.

Also updated tests, since the utility function gets confused by the
RRSIGs. Not fixing the function for now, it looks complicated, because
the problem is in it's design - if it happens to be just this one case,
it will be easier.

by update tests.  the semantics should be preserved at the moment.
making a commit at this point mainly as a checkpoint.

for database_unittests (due to too many conflicts).