mk-table-checksum and --since isn't working right on InnoDB tables

[GoogleCodeExporter]

If you run mk-table-checksum with MKDEBUG=1 on an InnoDB table, as follows,

mk-table-checksum --since 'current_date - interval 7 day'

and the table is

    Create_time: 2008-08-06 10:33:23
    Update_time: NULL
     Check_time: NULL
        Comment: InnoDB free: 2453504 kB;

Then you see

# main:3351 8478 Skipping table because --since value 2008-10-26 is newer
than 2008-09-26 08:31:32

Original issue reported on code.google.com by baron.schwartz on 2 Nov 2008 at 7:47

[GoogleCodeExporter]

I think I fixed this in r2471 and r2472 but we need a test case.

Original comment by baron.schwartz on 2 Nov 2008 at 9:11

• Changed state: Accepted

[GoogleCodeExporter]

Baron, After these changes (for issue 122 also), are the mk-table-checksum tests
passing for you? I just updated my copy of mk-table-check with the new 
MySQLFind for
issue 99 and I also have switched the test script to use the "universal 
sandbox", but
many of the tests are now failing. I don't know if it's 1) related to your 
changes,
2) my MySQLFind changes, or 3) the use of the universal sandbox.

Original comment by dan...@percona.com on 5 Nov 2008 at 4:18

[GoogleCodeExporter]

I don't know, I didn't run any tests -- I made the changes on a customer 
installation
and then put them into SVN.

Original comment by baron.schwartz on 5 Nov 2008 at 1:28

[GoogleCodeExporter]

Ok, in that case, I'll have to investigate mk-table-checksum further because it 
is
not a happy script. I'll begin by reverting my changes to see if the new 
MySQLFind or
the sandbox are the cause.

Original comment by dan...@percona.com on 5 Nov 2008 at 9:20

[GoogleCodeExporter]

I'm taking this issue and issue 122.

Original comment by dan...@percona.com on 7 Nov 2008 at 1:08

• Changed state: Started

[GoogleCodeExporter]

This is fixed and tested as of r2478. See issue 122 for more information.

Original comment by dan...@percona.com on 8 Nov 2008 at 3:50

• Changed state: Fixed