Showing 1-30 of 235 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
26115 | 2007-02-06 13:51 | 2007-02-06 17:28 | MySQL Server: Charsets | Closed (6260 days) | S3 | 5.0.32 | Linux (Debian arge/etch) | Any | Duplicated field value on different values (UTF8 string with 'o' and 'ó')? |
26436 | 2007-02-16 1:29 | 2007-12-21 9:27 | MySQL Server: Charsets | Closed (5942 days) | S3 | 5.0.34 | Windows (Windows) | Any | Bad handling of Cyrillic uppercase characters in table names on Windows |
28853 | 2007-06-03 1:29 | 2019-08-13 11:04 | MySQL Server: Charsets | Closed (6138 days) | S3 | Any | Any | MySQL must replace non-supported characters with reverse question mark | |
30803 | 2007-09-04 17:15 | 2007-09-04 17:45 | MySQL Server: Charsets | Closed (6050 days) | S3 | 5.0.46 | Any | Any | Unable to dump and re-read a mysqldump containing a latin1 146 char |
32831 | 2007-11-28 22:56 | 2011-02-16 23:43 | MySQL Server: Charsets | Closed (5525 days) | S2 | 5.1.22 | Windows | Any | libmysql should be built with all charsets |
34362 | 2008-02-06 19:59 | 2008-02-06 21:21 | MySQL Server: Charsets | Closed (5895 days) | S2 | 5.0.27 | Windows | Any | Loaded data appears to be duplicate but should not be |
35357 | 2008-03-18 5:14 | 2018-01-18 13:11 | MySQL Server: Charsets | Closed (2261 days) | S3 | 5.1.22, 5.1.23 | Windows | Any | character_set_database does not effects CREATE DATABASE without character set |
35588 | 2008-03-27 3:51 | 2008-05-02 17:23 | MySQL Server: Charsets | Closed (5809 days) | S2 | 5.0.22-log | Linux | Any | Incorrect work with character sets in stored functions |
38726 | 2008-08-11 19:08 | 2008-08-12 14:39 | MySQL Server: Charsets | Closed (5707 days) | S3 | 5.0.45 | Windows (XP SP2) | Any | spanish collation not working (latin1_spanish_ci) |
43055 | 2009-02-20 11:50 | 2011-02-16 23:43 | MySQL Server: Charsets | Closed (5515 days) | S2 | 5.0.32 | Any | Any | Connector/J causes data truncation error when inserting into latin1 text column |
43286 | 2009-03-01 10:30 | 2011-02-16 23:43 | MySQL Server: Charsets | Closed (5497 days) | S3 | 6.x | Any | Any | Endianness of unicode charsets |
45948 | 2009-07-04 18:06 | 2011-02-16 23:44 | MySQL Server: Charsets | Closed (5377 days) | S1 | 5.1.3x / 5.4.x | Any | Any | MySQL crashes with select statement (thai character in where clause) |
47641 | 2009-09-25 6:31 | 2014-09-24 7:58 | MySQL Server: Charsets | Closed (3501 days) | S3 | Any | Any | LIKE doesn't match when cp932_bin/sjis_bin collations are used | |
51675 | 2010-03-03 8:18 | 2011-02-16 23:44 | MySQL Server: Charsets | Closed (5132 days) | S3 | 5.5.3-m3 | Any | Any | Server crashes on inserting 4 byte char. after ALTER TABLE to 'utf8mb4' |
51676 | 2010-03-03 8:31 | 2011-02-16 23:44 | MySQL Server: Charsets | Closed (5132 days) | S3 | 5.5.3-m3 | Any | Any | Server crashes on SELECT, ORDER BY on 'utf8mb4' column |
53064 | 2010-04-22 13:57 | 2011-02-16 23:44 | MySQL Server: Charsets | Closed (4985 days) | S3 | next-mr-bar (2010-04-22) | Linux | Any | garbled data when using utf8_german2_ci collation |
59140 | 2010-12-23 18:29 | 2018-04-12 5:27 | MySQL Server: Charsets | Closed (4314 days) | S2 | 5.5.8 | Any | Any | LIKE concat('%',@a,'%') doesn't match when @a contains latin1 string |
59648 | 2011-01-21 7:52 | 2011-04-06 17:55 | MySQL Server: Charsets | Closed (4740 days) | S1 | mysql-trunk-debug | Any | Any | my_strtoll10_mb2: Assertion `(*endptr - s) % 2 == 0' failed. |
59735 | 2011-01-26 9:19 | 2011-04-02 1:35 | MySQL Server: Charsets | Closed (4744 days) | S3 | 5.5.8 | Any | Any | can't insert into value |
60625 | 2011-03-24 18:20 | 2011-04-28 16:08 | MySQL Server: Charsets | Closed (4718 days) | S3 | 5.5.10, 5.5.11 | Any | Any | Illegal mix of collations |
61034 | 2011-05-03 3:58 | 2018-01-18 13:16 | MySQL Server: Charsets | Closed (2261 days) | S3 | 5.5.11, 5.5.20 | Any (CENTOS 5.6 64bit, Mac OS X) | Any | "Illegal mix of collations for operation "By date datatype |
61986 | 2011-07-26 14:30 | 2018-04-11 11:55 | MySQL Server: Charsets | Closed (2178 days) | S3 | 5.5.16 | Linux | Any | Valgrind errors in various ctype tests 5.5 rev 3477 |
64328 | 2012-02-14 18:54 | 2012-02-15 12:48 | MySQL Server: Charsets | Closed (4425 days) | S3 | 5.5.19 | Any (tried rhel6 and Mac OS X 10.7) | Any | UTF8 characters S and ß considered identical |
64555 | 2012-03-05 21:28 | 2012-07-09 23:05 | MySQL Server: Charsets | Closed (4280 days) | S3 | 5.5.20 | Any | Any | Illegal mix of collations with functions that used to work |
65000 | 2012-04-16 21:30 | 2012-07-09 23:15 | MySQL Server: Charsets | Closed (4280 days) | S3 | 5.1.60, 5.5.20, 5.5.22 | Any | Any | Can't change collation_connection back from utf-16 to utf8 |
65593 | 2012-06-12 21:22 | 2013-01-22 15:20 | MySQL Server: Charsets | Closed (4083 days) | S3 | 5.5.21, 5.5.23 | Any | Any | parse errors in loadable UCA / LDML collations are silently ignored |
66721 | 2012-09-06 9:15 | 2012-09-12 19:32 | MySQL Server: Charsets | Closed (4215 days) | S3 | 5.6.6-m9-log | Windows | Any | SELECT INTO OUTFILE inconsistent with BOMs |
67359 | 2012-10-24 13:51 | 2012-10-24 16:31 | MySQL Server: Charsets | Closed (4173 days) | S2 | 5.5.13 | Linux (CentOS release 5.4) | Any | case/when statement with mixed collation makes mysqld crash |
68144 | 2013-01-22 15:18 | 2014-03-28 19:39 | MySQL Server: Charsets | Closed (3697 days) | S3 | mysql-5.6.9 | Any | Any | Collation name missing from log messages about LDML definition problems |
68366 | 2013-02-13 16:03 | 2018-01-18 13:19 | MySQL Server: Charsets | Closed (2261 days) | S5 | 5.5.29-0ubuntu0.12.10.1-log for debian- | Linux (Ubuntu 12.10) | Any | regression: >=mysql-5.4 utf8 collations are marked as not ascii compatible |
Showing 1-30 of 235 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |