Showing 1-30 of 89 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
25559 | 2007-01-11 22:52 | 2007-01-12 7:25 | MySQL Workbench Preview | Won't fix (6320 days) | S3 | 1.1.8 | Windows (windows) | Any | Reverse engineering does not pick up objects in information_schema |
65096 | 2012-04-25 1:44 | 2012-12-22 13:34 | MySQL Server: MyISAM storage engine | Won't fix (4149 days) | S1 | 5.1.62 | Any | Any | MyISAM Table Marked as Crashed During Query From INFORMATION_SCHEMA |
79370 | 2015-11-21 8:18 | 2017-10-09 8:45 | MySQL Server: Performance Schema | Won't fix (2397 days) | S3 | 5.7.9 | Any | Any | Change warning/error message regarding show_compatibility_56 |
97935 | 2019-12-10 2:01 | 2021-01-29 13:12 | MySQL Server: Information schema | Won't fix (1197 days) | S2 | 5.7.28 | Any | x86 | Memory leak in client connection using information_schema |
25630 | 2007-01-15 15:59 | 2018-09-09 20:45 | MySQL Server: Information schema | Verified (5397 days) | S3 | 5.0.33-standard-log/5.1BK | Linux (Centos 4.x) | Any | INFORMATION_SCHEMA collation wrong for filesystems with case sensitive filenames |
47961 | 2009-10-09 21:51 | 2011-02-16 23:44 | MySQL Server: Information schema | Verified (5319 days) | S3 | 5.1.39-community,5.5+ | Linux (only tested on CentOS 5.3) | Any | metadata leak from information_schema.routines via privs on mysql.proc table |
66414 | 2012-08-16 3:11 | 2023-07-26 14:24 | MySQL Server: Information schema | Verified (4250 days) | S3 | 5.5.16, 5.5.27 | Any | Any | incorrect quotation of statement in information_schema.TRIGGERS/ROUTINES |
71280 | 2014-01-02 18:21 | 2014-01-03 8:37 | MySQL Server: Information schema | Verified (3772 days) | S3 | 5.6.14, 5.6.15, 5.6.16 | Any | Any | Misleading error message for ANALYZE against INFORMATION_SCHEMA tables |
71312 | 2014-01-07 13:21 | 2014-01-08 12:27 | MySQL Server: Information schema | Verified (3767 days) | S3 | 5.6.15 | Any | Any | Weird warning for MERGE table while accessing I_S.REFERENTIAL_CONSTRAINTS |
71355 | 2014-01-12 17:22 | 2014-01-13 5:06 | MySQL Server: Information schema | Verified (3762 days) | S3 | 5.6 | Any | Any | Strange data type is used for name-related columns in some I_S.INNODB_* tables |
71470 | 2014-01-24 14:51 | 2014-01-26 11:10 | MySQL Server: InnoDB storage engine | Verified (3751 days) | S3 | 5.6.17 | Any | Any | Is ANALYZE TABLE supposed to reset I_S.INNODB_SYS_TABLESTATS.NUM_ROWS to 0? |
72912 | 2014-06-08 13:31 | 2014-06-08 19:38 | MySQL Server: Information schema | Verified (3616 days) | S3 | 5.6.19 | Any | Any | Inconsistent naming of tables in different I_S.innodb% tables |
74372 | 2014-10-14 11:38 | 2014-10-15 6:52 | MySQL Server: DML | Verified (3487 days) | S3 | Ver 14.14 Distrib 5.5.38, for debian-lin | Linux (3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux) | Any | SHOW CREATE TABLE shows not actual information |
75405 | 2015-01-04 22:30 | 2015-01-06 10:47 | MySQL Server: Information schema | Verified (3404 days) | S3 | 5.6.21, 5.6.23, 5.7.6 | Any | Any | I can't get from INFORMATION_SCHEMA original SQL code creating VIEW |
77191 | 2015-05-29 9:14 | 2015-05-29 11:30 | MySQL Server: Optimizer | Verified (3261 days) | S2 | 5.6.21, 5.6.24, 5.7.8 | Any | Any | Subquery on information_schema including an IN clause, does not return results |
83487 | 2016-10-23 8:40 | 2016-11-03 13:23 | MySQL Server: Information schema | Verified (2737 days) | S3 | 5.7.16, 5.6.34 | Windows | Any | INFORMATION_SCHEMA |
85787 | 2017-04-04 14:53 | 2017-04-04 17:42 | MySQL Server: Information schema | Verified (2585 days) | S3 | 5.6 and 5.7 | MacOS | Any | Inconsistent INFORMATION_SCHEMA across restarts after RENAME |
86930 | 2017-07-04 13:31 | 2017-07-11 19:14 | MySQL Server: Information schema | Verified (2494 days) | S3 | 5.6.29, 5.7.18 | Any | Any | Wrong results for queries with row constructors and information_schema |
90685 | 2018-04-30 7:41 | 2018-04-30 9:57 | MySQL Server: Information schema | Verified (2194 days) | S2 | tested 5.6, 5.7 and 8 | Windows | x86 (x64) | CHARACTER_MAXIMUM_LENGTH, CHARACTER_OCTET_LENGTH equal for multi-byte TEXT cols |
100607 | 2020-08-21 17:22 | 2022-12-19 19:08 | MySQL Server: Information schema | Verified (1347 days) | S2 | 8.0-8.0.21, 8.0.21, 8.0.11 | Linux | Any | Mysql escapes output where it shouldn't. Breaks schema generation tools |
110101 | 2023-02-16 15:32 | 2023-02-17 12:37 | MySQL Server: InnoDB storage engine | Verified (440 days) | S3 | 5.7.39, 8.0, 8.0.32 | Any | Any | lock_row_lock_current_waits counter in innodb_metrics goes negative |
48382 | 2009-10-28 16:12 | 2016-10-16 20:45 | MySQL Server: Replication | Verified | S2 | 5.1+ | Any | Any | mark reads from mysql.* and information_schema.* as unsafe |
40524 | 2008-11-05 11:25 | 2015-01-09 16:24 | MySQL Cluster: Cluster (NDB) storage engine | Unsupported (3401 days) | S2 | mysql-5.0 | Linux | Any | Wrong data in information_schema |
25346 | 2007-01-01 12:26 | 2007-06-14 12:58 | MySQL Cluster: Disk Data | Not a Bug (6167 days) | S3 | 5.1.14 | Linux (Linux) | Any | Disk-based information not available in INFORMATION_SCHEMA |
39778 | 2008-10-01 15:30 | 2008-10-02 15:21 | MySQL Server: Documentation | Not a Bug (5691 days) | S3 | 5.0+ | Any | Any | need clarification when user see full content of INFORMATION_SCHEMA.%_PRIVILEGES |
56071 | 2010-08-17 21:28 | 2010-08-17 21:33 | MySQL Workbench: Modeling | Not a Bug (5007 days) | S2 | 5.2.26 CE | Windows (x86 7 Ultimate) | Any | Information_schema doesn't show in object browser |
57192 | 2010-10-02 4:26 | 2010-10-02 7:19 | MySQL Server: InnoDB storage engine | Not a Bug (4961 days) | S3 | builtin, plugin | Any | Any | Primary key not accounted for in Index_length for InnoDB tables |
60161 | 2011-02-17 14:02 | 2011-02-17 17:07 | MySQL Server: Information schema | Not a Bug (4823 days) | S3 | 5.5 | FreeBSD | Any | Getting an error information_schema.routines |
59678 | 2011-01-23 9:14 | 2011-04-06 13:15 | MySQL Server: InnoDB storage engine | Not a Bug (4775 days) | S2 | 5.5.8, 5.6.2m5 | Any | Any | INFORMATION_SCHEMA.INNODB_TRX Does not contain all InnoDB transactions |
61670 | 2011-06-28 12:54 | 2011-06-29 3:37 | MySQL Server: Information schema | Not a Bug (4691 days) | S2 | Any | Any | Locked Transaction does not appear in I_S tables of InnoDB (5.1 plugin and 5.5) |
Showing 1-30 of 89 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |