Showing all 19 (Edit, Save, CSV, Feed) |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
21085 | 2006-07-16 21:33 | 2006-07-27 6:14 | MySQL Server: Charsets | Not a Bug (6476 days) | S3 | 5.0.25_BK, 5.0.21 | Linux (Red Hat Enterprise Linux ES rele) | Any | database collate set overriden by specifying only character set on column |
26073 | 2007-02-05 8:22 | 2007-02-21 16:18 | MySQL Query Browser | Closed (6267 days) | S3 | 1.2.9rc | Windows (Windows) | Any | Query Browser returns binary text (collation) columns as BLOB |
39242 | 2008-09-04 13:00 | 2008-09-06 15:05 | MySQL Server: Charsets | Can't repeat (5704 days) | S3 | 5.0.67 | Any | Any | Different result of 'like' operator |
42014 | 2009-01-10 14:46 | 2023-06-14 8:17 | MySQL Server: Data Types | Closed (5541 days) | S1 | 5.0.72, 5.0.76, 5.1.29, 5.1.30, 5.1.31, 6.0.10 | Any | Any | Crash, name_const with collate |
49712 | 2009-12-15 13:05 | 2009-12-15 13:25 | MySQL Server: Charsets | Not a Bug (5239 days) | S3 | 5.0.72 | Any | Any | bad search with utf8_polish_ci, and letter "รก" |
53896 | 2010-05-21 18:25 | 2011-02-16 23:44 | MySQL Workbench: Modeling | Closed (5068 days) | S3 | 5.2.21 RC | MacOS | Any | forward engineered ALTER scripts include collate info on numeric fields |
58585 | 2010-11-30 8:20 | 2010-11-30 23:07 | MySQL Server | Not a Bug (4889 days) | S3 | 5.0,5.1 (All?) | Any | Any | Collation bug when using if in where clause on string field |
58686 | 2010-12-03 0:16 | 2010-12-15 23:39 | MySQL Server | Not a Bug (4874 days) | S3 | 5.1.43sp1-enterprise-gpl | Any | Any | CREATE TABLE .. CHARSET=<...> without a COLLATE using case-insensitive collation |
62945 | 2011-10-26 15:47 | 2012-07-06 15:37 | MySQL Server: Charsets | Not a Bug (4305 days) | S3 | 5.5.15 | Any (7, x64) | Any | Like not work correctly for slovakian collate |
74055 | 2014-09-24 15:15 | 2014-10-02 14:16 | MySQL Workbench: Modeling | Closed (3487 days) | S3 | 6.0 | Windows (Community Edition) | Any | Charset and collate per column |
74920 | 2014-11-18 19:03 | 2014-11-18 21:05 | MySQL Server: Charsets | Not a Bug (3440 days) | S3 | 5.6.19-log | Linux (Amazon RDS) | Any | New tables ignore the default collate when a default charset is set |
76329 | 2015-03-15 21:07 | 2016-06-18 21:24 | MySQL Server: Parser | Closed (3202 days) | S3 | 5.7.6, 5.7.8, 8.0.0 | Any | Any | COLLATE option not accepted in generated column definition |
82132 | 2016-07-06 21:09 | 2016-09-02 2:05 | MySQL Server: Charsets | Closed (2786 days) | S1 | 5.7.13, 5.6.31 | Windows (Using MySQL Workbench version 6.3) | Any | STRCMP not consistent with ORDER BY for utf8mb4_unicode_ci |
32571 | 2007-11-21 13:03 | 2022-12-04 20:45 | MySQL Server: DDL | In progress (2567 days) | S3 | 5.0.37, 5.1, 5.6, 5.7 | Linux (Windows, Ubuntu) | Any | CREATE TABLE options are dependant on the order of specification |
106099 | 2022-01-07 13:35 | 2022-01-07 14:21 | MySQL Server | Can't repeat (833 days) | S3 | 8.0.21 | Windows (MS Windows 10 Home) | Any | Case sensitivity not recognised when adding unique index to re-collated column |
111328 | 2023-06-08 8:08 | 2023-06-09 12:08 | MySQL Server: DDL | Verified (315 days) | S3 | 8.0 | Any | Any | utf8mb4_0900_ai_ci be added to Column definition when convert table to utf8mb4 |
113562 | 2024-01-05 1:14 | 2024-01-09 21:52 | MySQL Server: DDL | Not a Bug (101 days) | S3 | 8.2.0, 8.0.35 | Debian | Any | COLLATION behaves differently if set on CREATE TABLE vs ALTER TABLE |
114152 | 2024-02-28 7:53 | 2024-02-29 10:50 | MySQL Server: Command-line Clients | Can't repeat (50 days) | S2 | mysqldump Ver 8.0.36-0ubuntu0.22.04.1 | Ubuntu (Pop!_OS 22.04 LTS) | x86 (Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz) | Invalid mysqldump file generated for some views with collate statements |
114445 | 2024-03-21 14:12 | 2024-03-22 8:42 | MySQL Server: DDL | Verified (28 days) | S3 | 8.3.0 | Ubuntu (Ubuntu 22.04) | x86 (x86_64) | Possibly missing keyword escape |
Showing all 19 (Edit, Save, CSV, Feed) |