Bug #10493 SJIS char fields not correctly saved
Submitted: 9 May 2005 20:09 Modified: 6 Jun 2005 8:29
Reporter: Geert Vanderkelen Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server Severity:S1 (Critical)
Version:4.1.11 OS:
Assigned to: Alexey Botchkov
Tags: corruption, myisam

[9 May 2005 20:09] Geert Vanderkelen
Description:
Hi,

When updating char/varchar fields using SJIS encoding the end of the field is not correctly set and following fields are getting corrupt.
Putting the character field containing SJIS data at the end, causes the table to be marked as crashed.

Regards,

Geert

How to repeat:
Attaching.
[9 May 2005 21:17] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/24754
[9 May 2005 22:41] Alexey Botchkov
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html
[12 May 2005 12:08] Geert Vanderkelen
Smaller test script

Attachment: simpletest.sql (text/x-sql), 338 bytes.

[12 May 2005 12:18] Geert Vanderkelen
Same problem in 5.0 (beta and latest pull). I have attached a smaller test script.

I Asked DocTeam to document in ChangeLog the bugfix for 4.1.12.

Regards,

Geert
[13 May 2005 17:23] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/24876
[20 May 2005 14:46] Paul Dubois
4.1 fix noted in 4.1.12 changelog.