| Showing all 10 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 21031 | 2006-07-13 11:55 | 2006-10-26 13:38 | MySQL Server: Memory storage engine | Not a Bug (6384 days) | S3 | 5.0.21 | Any (any) | Any | Alter table to memory table defaults to hash indexes |
| 30293 | 2007-08-08 7:00 | 2007-08-18 8:48 | MySQL Server: Memory storage engine | Not a Bug (6088 days) | S3 | 5.1.20, 5.0 , 4.1 BK | Any | Any | memory tables with btree indexes .. very weird situation |
| 39766 | 2008-10-01 2:31 | 2008-10-23 23:04 | MySQL Server: Memory storage engine | Not a Bug (5656 days) | S2 | 5.0.60-log, 5.0.66a, 5.1.28 | Any | Any | Physical order of rows in table alters update behavior of unique index |
| 57725 | 2010-10-26 4:20 | 2010-11-11 0:13 | MySQL Server: Memory storage engine | Not a Bug (4907 days) | S2 | 5.1.51 | Any | Any | Memory Storage Engine not to keep the auto_increment value of table option |
| 21846 | 2006-08-26 1:43 | 2006-09-05 14:32 | MySQL Server: Memory storage engine | Not a Bug (6435 days) | S3 | 5.0.25-BK, 5.0.24 | Linux (Linux, Windows) | Any | Query with memory table returns different results if indexed |
| 23992 | 2006-11-05 23:10 | 2010-08-18 9:38 | MySQL Server: Memory storage engine | Not a Bug (6366 days) | S3 | 5.0.30-BK, 5.0.26 | Linux (Debian GNU/Linux Sid) | Any | "CREATE TABLE .. IF NOT EXISTS" confusion |
| 37785 | 2008-07-01 21:47 | 2008-07-02 17:27 | MySQL Server: Memory storage engine | Not a Bug (5769 days) | S3 | mysql-6.0-backup, mysql-maria | Linux | Any | Order by works different for Memory storage engine |
| 94646 | 2019-03-14 2:47 | 2019-03-15 2:12 | MySQL Server: Memory storage engine | Not a Bug (1861 days) | S3 | 5.7.23 & 8.0.13 | Linux | Any | An alteration of the system variable "max_heap_table_size" does not take effect? |
| 33473 | 2007-12-21 21:35 | 2007-12-22 21:30 | MySQL Server: Memory storage engine | Not a Bug (5962 days) | S3 | 5.1.22 | MacOS | Any | MEMORY engine doesn't honor MAX_ROWS correctly |
| 94647 | 2019-03-14 4:45 | 2019-03-28 5:31 | MySQL Server: Memory storage engine | Not a Bug (1861 days) | S3 | 5.7 | Debian | Any | Memory leak in MEMORY table by glibc |
| Showing all 10 (Edit, Save, CSV, Feed) |
