| Bug #26238 | inserted delayed always inserts 0 for BIT columns | ||
|---|---|---|---|
| Submitted: | 9 Feb 2007 22:21 | Modified: | 15 Mar 2007 4:20 |
| Reporter: | Shane Bester | ||
| Status: | Closed | ||
| Category: | Server: General | Severity: | S1 (Critical) |
| Version: | 5.0.36 | OS: | Any (*) |
| Assigned to: | Sergey Vojtovich | Target Version: | |
| Tags: | insert delayed, bit | ||
[9 Feb 2007 22:21]
Shane Bester
[28 Feb 2007 15:35]
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/commits/20780 ChangeSet@1.2418, 2007-02-28 18:34:35+04:00, svoj@mysql.com +3 -0 BUG#26238 - inserted delayed always inserts 0 for BIT columns INSERT DELAYED inserts garbage for BIT columns. When delayed thread clones TABLE object, it didn't adjusted bit_ptr to newly created record (though it correctly adjusts ptr and null_ptr). This is fixed by correctly adjusting bit_ptr when performing a clone. With this fix BIT values are stored correctly by INSERT DELAYED.
[1 Mar 2007 11:48]
Ingo Strüwing
This seems to be (almost) a backport from 5.1. However in 5.1 we use a slightly different method for the same purpose. I approve the patch. But please do a null-merge to 5.1.
[1 Mar 2007 12:20]
Ingo Strüwing
Switched to "In review" for Ramil, btw.
[14 Mar 2007 9:55]
Sergey Vojtovich
Fixed in 5.0.38, 5.1.17.
[15 Mar 2007 4:20]
Paul DuBois
Noted in 5.0.38, 5.1.17 changelogs.
