Bug #43725 | Innodb different on hex() results for bit type | ||
---|---|---|---|
Submitted: | 18 Mar 2009 11:28 | Modified: | 23 Apr 2009 10:03 |
Reporter: | Nidhi Shrotriya | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
Version: | 6.0.11/5.0/5.1 | OS: | Any |
Assigned to: | Marko Mäkelä | CPU Architecture: | Any |
[18 Mar 2009 11:28]
Nidhi Shrotriya
[18 Mar 2009 11:29]
Nidhi Shrotriya
Test Case
Attachment: bit_bug_innodb_43725.test (application/octet-stream, text), 2.84 KiB.
[18 Mar 2009 13:17]
MySQL Verification Team
Thank you for the bug report. Verified as described.
[19 Mar 2009 22:47]
Mikhail Izioumtchenko
whatever was meant by test case 1 is either not there any longer or I failed to understand it. However I reproduced the attached testcase for multitable update with our r4482. Innodb likes to make the two column values equal which makes me thing it's a duplicate of bug#4580
[19 Mar 2009 23:02]
Mikhail Izioumtchenko
sorry, it was bug#43580 I meant, not 4580
[23 Apr 2009 10:03]
Marko Mäkelä
I can't repeat the first problem in the InnoDB Plugin (using MySQL 5.1.28-bzr) or in MySQL 6.0.11-bzr. If the second problem (multi-table update) is a duplicate of Bug #43580, it seems to be a bug in the MySQL layer, outside InnoDB.