-
Manish Kumar authored
INCORRECTLY. Description: When mysqlbinlog --hexdump prints events, it prints the last row of the hexdump incorrectly, in two ways: 1. if the last row has eight bytes, the end of the second last row is copied to the end of the last row, padding the last row to full length. 2. if the last row has less than sixteen bytes, the textual representation is not aligned with previous rows. Problem: there was no proper alignment done incase the last line had less than 16 bytes. Fix: the bug was removed by padding the last line with the required number of spaces.
Manish Kumar authoredINCORRECTLY. Description: When mysqlbinlog --hexdump prints events, it prints the last row of the hexdump incorrectly, in two ways: 1. if the last row has eight bytes, the end of the second last row is copied to the end of the last row, padding the last row to full length. 2. if the last row has less than sixteen bytes, the textual representation is not aligned with previous rows. Problem: there was no proper alignment done incase the last line had less than 16 bytes. Fix: the bug was removed by padding the last line with the required number of spaces.
Loading