You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Kathey Marsden <km...@sbcglobal.net> on 2009/05/22 21:09:27 UTC

store/oc_rec2.java table names

I was looking at the oc_rec2 tests, because it was the test that exposed 
DERBY-4239.
and noticed this code in the test1 method ...

 // make sure we can add data to the existing table after redo
        // recovery.
        createAndLoadTable(conn, false, table_name, 6000, 0);
        if (!checkConsistency(conn, "APP", table_name))
        {
            logError("conistency check failed.");
        }

        // setup to test redo recovery on:
        //     create table, delete rows, compress, add rows, commit
        String table_name_2 =  table_name + "_2";
        createAndLoadTable(conn, true, table_name_2, 2000, 0);
-->        executeQuery(conn, "delete from " + table_name, true);
-->        callCompress(conn, "APP", table_name, true, true, true, true);

I wonder if the delete and the compress were intended to be run on 
table_name_2 not table_name as this looks like it may be a cut and paste 
error.  Then again, I may just not be getting the point of the test and 
this may be intentional.

Kathey