Showing 1-30 of 92 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
52520 | 2010-04-01 10:57 | 2011-02-16 23:44 | MySQL Server: Charsets | Closed (4811 days) | S3 | 5.5.3-m3 | Any | Any | Difference in tinytext utf column metadata |
43620 | 2009-03-13 6:34 | 2009-05-07 8:32 | MySQL Server: Maria storage engine | Closed (5251 days) | S3 | 6.0.11-bzr | Any | Any | Maria throws 'Got error 176 from storage engine' on a range query |
43668 | 2009-03-16 8:59 | 2011-02-16 23:43 | MySQL Server: Data Types | Closed (4942 days) | S3 | 6.0.11,5.4,5.1 | Any | Any | Server returns wrong MAX() value with year(2) type and no index |
43669 | 2009-03-16 9:16 | 2013-11-19 18:19 | MySQL Server: Data Types | Unsupported (3594 days) | S3 | 6.0.11 | Any | Any | Falcon returns diff. no of digits than other engines with MIN() for YEAR values |
43690 | 2009-03-17 8:02 | 2010-05-26 18:00 | MySQL Server: Falcon storage engine | Unsupported (4867 days) | S3 | 6.0.11 | Any | Any | Falcon gives wrong error & add warnings on updating for cols. in where clause |
43696 | 2009-03-17 10:38 | 2009-03-17 11:03 | MySQL Server: InnoDB storage engine | Not a Bug (5302 days) | S3 | 6.0.11, 5.0, 5.1 bzr | Any | Any | Innodb different from other engines on delete time data type |
43720 | 2009-03-18 6:00 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5301 days) | S3 | 6.0.11, 5.0, 5.1 bzr | Any | Any | MyISAM & Maria gives wrong results with range access on bit type |
43725 | 2009-03-18 11:28 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Can't repeat (5265 days) | S3 | 6.0.11/5.0/5.1 | Any | Any | Innodb different on hex() results for bit type |
43763 | 2009-03-20 6:30 | 2011-02-16 23:43 | MySQL Server | Verified (5299 days) | S3 | 6.0.11, 5.0, 5.1, 6.0 bzr | Any | Any | Difference in warnings generated between engines |
55579 | 2010-07-27 8:42 | 2010-07-27 8:57 | MySQL Server | Not a Bug (4805 days) | S3 | 5.1.49 | Any | Any | 'CREATE TABLE IF NOT EXISTS' behaves different with jdbc Vs. mysql client |
55499 | 2010-07-23 8:13 | 2011-02-16 23:44 | MySQL Server | Closed (4725 days) | S3 | 5.1-wl5370 | Any | Any | Wrong binlog(Repl. breaks) with 'CREATE TABLE IF NOT EXISTS' & tbl prefix schema |
55474 | 2010-07-22 9:24 | 2011-02-16 23:44 | MySQL Server | Closed (4725 days) | S3 | 5.1-wl5370 | Any | Any | Replication diff and 'no warning' for Views when WL#5370 included in 5.1 |
54278 | 2010-06-07 8:58 | 2012-05-18 20:19 | MySQL Server: Charsets | Verified | S3 | 5.5.4-m3, 5.0 | Any | Any | Illegal mix of collations on downgrading views based on 'utf8mb4' tables |
52522 | 2010-04-01 11:43 | 2011-02-16 23:44 | MySQL Server: Security: Privileges | Duplicate (4873 days) | S3 | 5.5.3-m3 | Any | Any | Running mysql_upgrade loses trigger privileges |
46876 | 2009-08-24 4:59 | 2011-02-16 23:44 | MySQL Server: Replication | Won't fix (5139 days) | S3 | 5.0 | Any | Any | Mix of transactional and non-transactional tables causes failure in replication |
43623 | 2009-03-13 8:22 | 2009-05-07 8:31 | MySQL Server: Maria storage engine | Closed (5251 days) | S3 | 6.0.11-bzr | Any | Any | Maria returns no rows with date index on range access >, >=, BETWEEN |
52470 | 2010-03-30 11:42 | 2011-02-16 23:44 | MySQL Server: DDL | Unsupported (4917 days) | S3 | 5.5.3-m3 | Any | Any | Corrupt table comments and length on downgraded table with long comments |
47910 | 2009-10-08 8:14 | 2011-02-16 23:44 | MySQL Server: Command-line Clients | Verified (4918 days) | S3 | 5.1.45 | Any | Any | Mysql client Segfaults on query 2 byte coll id with column-type-info enabled |
48077 | 2009-10-15 12:04 | 2022-12-04 20:45 | MySQL Server: DDL | Verified (5089 days) | S3 | 6.0.14, 5.5.3-m3, 5.1.47 | Any | Any | Issues with warnings on adding long comments to table/col/index after upgrade |
48721 | 2009-11-12 9:03 | 2009-11-25 22:39 | MySQL Server: Security: Privileges | Not a Bug (5049 days) | S3 | 5.5.0->5.1 | Any | Any | New create_tablespace_priv column exists in mysql.user, after downgrade to 5.1 |
48722 | 2009-11-12 10:36 | 2011-02-16 23:44 | MySQL Server: Documentation | Closed (4684 days) | S3 | 5.5.0 | Any | Any | SIGNAL/RESIGNAL usage and error nos. not documented ? |
49134 | 2009-11-26 11:03 | 2011-02-16 23:44 | MySQL Server: Charsets | Closed (4942 days) | S3 | 5.1.41 | Any | Any | 5.1 server segfaults with 2byte collation file |
52444 | 2010-03-29 15:42 | 2011-02-16 23:44 | MySQL Server: Stored Routines | Closed (4885 days) | S3 | 5.5.3-m3 | Any | Any | mysql_upgrade fails b/w 5.1 -> 5.5 (Celosia) |
51676 | 2010-03-03 8:31 | 2011-02-16 23:44 | MySQL Server: Charsets | Closed (4944 days) | S3 | 5.5.3-m3 | Any | Any | Server crashes on SELECT, ORDER BY on 'utf8mb4' column |
51675 | 2010-03-03 8:18 | 2011-02-16 23:44 | MySQL Server: Charsets | Closed (4944 days) | S3 | 5.5.3-m3 | Any | Any | Server crashes on inserting 4 byte char. after ALTER TABLE to 'utf8mb4' |
50655 | 2010-01-27 11:14 | 2012-10-25 1:00 | MySQL Server: Charsets | No Feedback (3984 days) | S3 | 5.6, 6.1 | Any | Any | Replication fails after setting 'SET NAMES utf8' with NM(5.6) -> OS(5.1) |
50238 | 2010-01-11 15:08 | 2022-12-04 20:45 | MySQL Server: Security: Privileges | Verified | S3 | 5.5.1-m2 | Any | Any | 'GRANT SUPER' doesn't give 'TABLESPACE' priv in fresh 5.5, upgrade from 5.1 does |
50183 | 2010-01-08 11:37 | 2011-02-16 23:44 | MySQL Server: Documentation | Closed (4958 days) | S3 | 5.5.1-m2 | Any | Any | mysql.proc table needs repair (corrupt) after dump downgrade from 5.5 -> 5.1 |
49888 | 2009-12-23 9:12 | 2011-02-16 23:44 | MySQL Server: Charsets | Can't repeat (4937 days) | S3 | 5.6 | Any | Any | mysql db tables converted from utf8mb3 to utf8, put lot errors in server log |
49583 | 2009-12-10 12:14 | 2011-02-16 23:44 | MySQL Workbench | Can't repeat (4979 days) | S3 | 5.2.10 | Any | Any | Can't stop server started outside workbench |
Showing 1-30 of 92 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |