Showing all 30 (Edit, Save, CSV, Feed) |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
42531 | 2009-02-02 5:49 | 2014-02-21 19:35 | Obsolete | Unsupported (3689 days) | S3 | 5.1.30 | Other (IBMi 5.4) | Any | 'CREATE TABLE t1(M-PM-:M-PM->M-PM-; INT)' fails with ibmdb2i |
42532 | 2009-02-02 6:16 | 2013-02-02 11:27 | Obsolete | Unsupported (4073 days) | S3 | 5.1.30 | Other (IBMi 5.4) | Any | IBMDB2i doesn't throw ER_DUP_ENTRY, where it is expected to throw |
42746 | 2009-02-11 6:01 | 2014-02-21 19:35 | Obsolete | Unsupported (3689 days) | S3 | 5.1.30 | Other (IBM i 5.4) | Any | CREATE fails when the table creates a foreign key, referencing to some table. |
46893 | 2009-08-24 13:02 | 2012-05-18 20:19 | MySQL Server | No Feedback (5242 days) | S3 | 5.1.38 | Linux | Any | Performance degradation on SuSE-10/RHEL in dbt2 test |
56137 | 2010-08-20 8:12 | 2011-02-16 23:44 | MySQL Server | Closed (4885 days) | S3 | 5.5.6-m3-debug | Any | Any | Assertion `thd->lock == 0' failed on upgrading from 5.1.50 to 5.5.6 |
42528 | 2009-02-02 5:19 | 2009-05-13 6:54 | MySQL Server: DB2SE for IBM i | Closed (5434 days) | S3 | 5.1.30 | Other (IBMi 5.4) | Any | SELECT fails when executed in sequence after lock & flush table with ibmdb2i |
42530 | 2009-02-02 5:38 | 2009-04-21 6:34 | MySQL Server: DB2SE for IBM i | Closed (5456 days) | S3 | 5.1.30 | Other (IBMi 5.4) | Any | ALTER TABLE fails when charset is changed from hebrew to utf8 with ibmdb2i |
42533 | 2009-02-02 6:44 | 2009-08-05 8:05 | MySQL Server: DB2SE for IBM i | Closed (5350 days) | S3 | 5.1.30 | Other (IBMi 5.4) | Any | SELECT shows only 'null',when various values inserted to UNIQUE(a),with ibmdb2i |
42527 | 2009-02-02 4:57 | 2009-05-13 6:46 | MySQL Server: DB2SE for IBM i | Closed (5434 days) | S3 | 5.1.30 | Other (IBMi 5.4) | Any | SELECT length(data) fails with ibmdb2i when max_allowed_packet=64*1024*1024 |
48362 | 2009-10-28 7:01 | 2013-12-20 12:20 | MySQL Server: DDL | Closed (3752 days) | S4 | 5.1 and 5.4 | Any | Any | Comment in index definition in table definition is not supported. |
51863 | 2010-03-09 11:33 | 2011-02-16 23:44 | MySQL Server: Documentation | Closed (5126 days) | S3 | 5.1.44 | Any | Any | Difference in SELECT output for large floating-pt numbers on SunOS and Linux |
58060 | 2010-11-08 19:06 | 2011-02-16 23:44 | MySQL Server: Information schema | Verified (4880 days) | S3 | 5.5.7-rc-debug | Any | Any | Inconsistency in row format reported through I_S |
52056 | 2010-03-15 8:36 | 2018-09-23 20:45 | MySQL Server: InnoDB Plugin storage engine | Duplicate (5128 days) | S3 | 5.1.45, 5.5.1-m2, 5.5.3-m2 | Any | Any | Creating unique index on blob/not null column of innodbplugin table throws error |
52183 | 2010-03-18 15:27 | 2016-12-08 9:14 | MySQL Server: Installing | Won't fix (2668 days) | S3 | 5.1.45 | Windows | Any | Host lookup fails for mysql_install_db on windows |
58483 | 2010-11-25 10:21 | 2011-02-01 14:55 | MySQL Server: Installing | Not a Bug (4805 days) | S3 | Any | Any | Any | Scripts under /bin should move to /scripts |
52283 | 2010-03-22 19:10 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5120 days) | S3 | 5.1.46 | Any | Any | Innodb reports extra warnings when SELECT/WHERE is performed using invalid value |
52303 | 2010-03-23 13:52 | 2010-04-13 5:29 | MySQL Server: Optimizer | Not a Bug (5099 days) | S3 | 5.1.46, 5.5.1-m2, 5.5.3-m3 | Any | Any | MIN() outputs 0 as the minimum year(4) corresponding to 0000 |
55648 | 2010-07-30 12:21 | 2011-02-16 23:44 | MySQL Server: Optimizer | Closed (4875 days) | S3 | 5.5.6-m3-debug | Any | Any | Server crashes when subjected to max/min on a table containing max allowed TIME |
56120 | 2010-08-19 14:10 | 2011-02-16 23:44 | MySQL Server: Optimizer | Closed (4926 days) | S3 | 5.5.6-m3, 5.6.99-m5 | Any | Any | Assertion `time <= (838*10000 + 59*100 + 59)' failed on negative TIME |
56962 | 2010-09-23 7:26 | 2012-04-03 17:40 | MySQL Server: Optimizer | Closed (4378 days) | S3 | 5.6.99-m5 | Any | Any | Inconsistent 'Out of range' warning message on select |
58719 | 2010-12-03 19:05 | 2010-12-15 12:13 | MySQL Server: Optimizer | Not a Bug (4853 days) | S3 | mysql-5.5.8 | Any | Any | Server does not report ER_SP_FETCH_NO_DATA warning any more |
58600 | 2010-11-30 17:20 | 2011-02-16 23:44 | MySQL Server: Tests | Closed (4827 days) | S3 | mysql-5.5-bugteam | Any | Any | main.not_embedded_server test does not cleanup properly |
50293 | 2010-01-12 22:23 | 2010-01-14 23:41 | MySQL Server: Data Types | Not a Bug (5188 days) | S3 | 5.1-bugteam, 5.5.99 | Any | Any | Difference in SELECT output when search is based on an invalid DATE/DATETIME |
52430 | 2010-03-29 11:01 | 2011-02-16 23:44 | MySQL Server: Data Types | Closed (5014 days) | S3 | 5.5.3-m3 | Any | Any | Incorrect key in the error message for duplicate key error involving BINARY type |
52824 | 2010-04-14 14:08 | 2018-09-09 20:45 | MySQL Server: Data Types | Duplicate (4928 days) | S3 | 5.5.5-m3 | Any | Any | Comparing DATE against the result of ADDTIME is inconsistent, non-deterministic |
50231 | 2010-01-11 13:10 | 2011-02-16 23:44 | MySQL Server: Data Types | Can't repeat (5187 days) | S3 | 5.1-bugteam | Any | Any | Select shows different outputs for 'bigint' column containing 'null' values |
49910 | 2009-12-24 6:13 | 2011-02-16 23:44 | MySQL Server: Data Types | Closed (4797 days) | S3 | 5.1.42, next-mr | Any | Any | Behavioural change in SELECT/WHERE on YEAR(4) data type |
56964 | 2010-09-23 8:32 | 2011-03-15 11:32 | Tools: MTR / mysql-test-run | Closed (4763 days) | S3 | 5.6.1-m4 | Any | Any | Replication test's state affecting subsequent rpl tests |
49978 | 2009-12-29 14:26 | 2011-02-16 23:44 | Tools: MTR / mysql-test-run | Closed (4838 days) | S3 | 5.1.42 | Any | Any | Replication tests don't clean up replication state at the end |
58718 | 2010-12-03 18:53 | 2011-02-16 23:44 | Tools: MTR / mysql-test-run | Closed (4798 days) | S3 | mysql-5.5, 5.6.1 | Any | Any | Second rpl test sporadically fails with error 1220 |
Showing all 30 (Edit, Save, CSV, Feed) |