Bug #30282 | Falcon: duplicate-key error for value that ends with 0x00 | ||
---|---|---|---|
Submitted: | 7 Aug 2007 18:42 | Modified: | 18 Dec 2008 14:13 |
Reporter: | Peter Gulutzan | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server: Falcon storage engine | Severity: | S2 (Serious) |
Version: | 6.0-falcon | OS: | Any |
Assigned to: | Assigned Account | CPU Architecture: | Any |
Tags: | F_ENCODING |
[7 Aug 2007 18:42]
Peter Gulutzan
[11 Aug 2007 18:15]
MySQL Verification Team
Thank you for the bug report. Verified as described.
[21 Aug 2007 16:00]
Hakan Küçükyılmaz
Added test case falcon_bug_30282.test and pushed to 5.1-falcon tree.
[3 Jan 2008 16:48]
Philip Stoev
This bug affects the ujs character set. To reproduce, run: perl mysql-test-run.pl --mysqld=--default-storage-engine=falcon ctype_ujis_ucs2
[26 Jun 2008 21:53]
Kevin Lewis
Another character-set related bug.
[18 Dec 2008 9:32]
Lars-Erik Bjørk
I am pretty sure that this is a duplicate of bug#34479 Falcon: search failure with indexed ucs2 varchar. I have also tested the reported queries against a sandbox version containing an incomplete fix for 34479 (will fail for like searches and multi-field keys) and the problem is not reproducible there. I will look a little deeper and probably close as a duplicate.
[18 Dec 2008 14:13]
Lars-Erik Bjørk
It seems that MySQLCollation::computeKeyLength returns a length of 0 for both of these values, because it is removing trailing spaces regardless of the charset, as well as removing trailing zeroes. I am closing this as a duplicate of bug#34479