BIND 10 trac1899, created. 9cf67e85ab39694505798d59a7264172de678a14 [1899] Merge records and nsec3 tables correctly (see previous commit)

[BIND 10 source code commits]

The branch, trac1899 has been created
        at  9cf67e85ab39694505798d59a7264172de678a14 (commit)

- Log -----------------------------------------------------------------
commit 9cf67e85ab39694505798d59a7264172de678a14
Author: Mukund Sivaraman <muks at isc.org>
Date:   Wed Sep 26 04:48:38 2012 +0530

    [1899] Merge records and nsec3 tables correctly (see previous commit)

commit 11c873d5cd0cc9b469e8c1fc95b28ced03840d09
Author: Mukund Sivaraman <muks at isc.org>
Date:   Wed Sep 26 03:34:56 2012 +0530

    [1899] Break up UNION SQL query into two and merge manually
    
    We also add a new index nsec3_byowner_and_rdtype, but don't bump
    the SQL schema (the plan is to merge #1756 which bumps schema
    version and #1899 together so that two schema version changes are
    not necessary).
    
    Note that this still is buggy code, and it has always been buggy
    because it tries to merge rname (reversed name) from the records
    table with owner column in the nsec3 table. So you have results
    out of order. There was no unit test to check if both sides of
    the UNION were being merged properly before.
    
    We'd have to fix this by adding nsec3.rowner column.

-----------------------------------------------------------------------