the tool can't handle string types CHAR(X) encoded in UTF-8

Bug #624460 reported by Aleksandr Kuzminsky on 2010-08-26
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Data Recovery Tool for InnoDB
Aleksandr Kuzminsky

Bug Description

VARCHAR() and CHAR() types are used to store strings.
Apparently VARCHAR() is variable length type while CHAR() is fixed size.
VARCHAR() has got a length in OFFSETs header. CHAR() - doesn't.

However in some cases InnoDB internally stores VARCHAR() as CHAR() and CHAR() as VARCHAR().
For expample, CHAR() is variable when a table's encoding is UTF-8.
Not clean in what cases VARCHAR() is fixed though.

The tool can't detect such cases, so can't recover the records.
The sympthoms might be strings without ending " or without first characters.

Changed in percona-innodb-recovery-tool:
assignee: nobody → Aleksandr Kuzminsky (akuzminsky)
importance: Undecided → High
summary: - the tool can't handle string types when stored in unexpected way
+ the tool can't handle string types CHAR(X) encoded in UTF-8
Changed in percona-data-recovery-tool-for-innodb:
milestone: none → release-0.5
Changed in percona-data-recovery-tool-for-innodb:
status: New → In Progress
Changed in percona-data-recovery-tool-for-innodb:
status: In Progress → Fix Committed
Changed in percona-data-recovery-tool-for-innodb:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers