| « Show Previous 30 Entries | Showing 31-60 of 61 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 44138 | 2009-04-07 22:48 | 2016-06-09 7:33 | MySQL Server: Memory storage engine | Verified (3791 days) | S2 | 5.1.57, 5.6.14, 5.6.30 | Linux (x86_64 rhel5 version from download page) | Any | Memory engine table full at much less than max_heap_table_size with btree index |
| 42868 | 2009-02-15 20:00 | 2013-03-03 20:45 | MySQL Server: Memory storage engine | Verified (5539 days) | S3 | 5.0.74, 5.1.48 | Any | Any | unique prefixed indexes on varchar columns don't work in memory engine |
| 41549 | 2008-12-17 14:27 | 2011-02-16 23:43 | MySQL Server: Memory storage engine | No Feedback (5542 days) | S2 | 4.0.27-max-log | Linux (Debian Etch) | Any | MySQL crashes with segmentation fault in ha_heap::rnd_next() |
| 39918 | 2008-10-07 22:59 | 2011-02-16 23:43 | MySQL Server: Memory storage engine | Closed (5409 days) | S2 | 5.0.67, 5.1.30-bzr | Any | Any | memory (heap) engine crashing with b-tree index and DELETE with seg fault |
| 39886 | 2008-10-06 15:12 | 2011-02-16 23:43 | MySQL Server: Memory storage engine | Closed (5549 days) | S3 | 5.0,5.1 | Any | Any | Table full for MEMORY table is not written into error log |
| 39766 | 2008-10-01 2:31 | 2008-10-23 23:04 | MySQL Server: Memory storage engine | Not a Bug (5654 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 |
| 37785 | 2008-07-01 21:47 | 2008-07-02 17:27 | MySQL Server: Memory storage engine | Not a Bug (5767 days) | S3 | mysql-6.0-backup, mysql-maria | Linux | Any | Order by works different for Memory storage engine |
| 33473 | 2007-12-21 21:35 | 2007-12-22 21:30 | MySQL Server: Memory storage engine | Not a Bug (5960 days) | S3 | 5.1.22 | MacOS | Any | MEMORY engine doesn't honor MAX_ROWS correctly |
| 31445 | 2007-10-08 12:12 | 2012-05-18 20:19 | MySQL Server: Memory storage engine | Duplicate (6021 days) | S2 | 5.0.45 | Windows (Linux) | Any | Delete only deletes first matching record |
| 30885 | 2007-09-07 7:17 | 2007-10-24 20:03 | MySQL Server: Memory storage engine | Closed (6019 days) | S2 | 5.0.50-bk | Any | Any | MEMORY returns incorrect data if BTREE index is used for NULL lookup |
| 30590 | 2007-08-23 10:26 | 2010-05-12 10:44 | MySQL Server: Memory storage engine | Closed (6021 days) | S1 | 5.0.48,5.1.22 | Any | Any | delete from memory table with composite btree primary key |
| 30293 | 2007-08-08 7:00 | 2007-08-18 8:48 | MySQL Server: Memory storage engine | Not a Bug (6086 days) | S3 | 5.1.20, 5.0 , 4.1 BK | Any | Any | memory tables with btree indexes .. very weird situation |
| 30197 | 2007-08-02 6:35 | 2007-09-02 8:01 | MySQL Server: Memory storage engine | No Feedback (6071 days) | S1 | 5.0.14 | Windows (XP SP2) | Any | mysqlnt memory access violation error |
| 30090 | 2007-07-27 6:23 | 2012-05-18 20:19 | MySQL Server: Memory storage engine | Duplicate (5978 days) | S3 | 5.0.44 | Any | Any | DELETE from MEMORY table with BTREE primary key extremely slow |
| 29349 | 2007-06-26 1:01 | 2014-02-02 14:12 | MySQL Server: Memory storage engine | Verified (6138 days) | S3 | 5.0.27 | Any | Any | dropping MEMORY table very slow |
| 29342 | 2007-06-25 17:33 | 2007-07-25 18:49 | MySQL Server: Memory storage engine | No Feedback (6110 days) | S3 | 5.1.14-beta | Windows | Any | Unsupported query executed by Brighthouse(storage engine) with no error message. |
| 29168 | 2007-06-18 9:07 | 2007-12-25 16:19 | MySQL Server: Memory storage engine | No Feedback (5957 days) | S3 | 5.1 bk | Any | Any | Error: Freeing pointer out of range at line 148, 'hp_block.c' |
| 26996 | 2007-03-09 12:44 | 2007-03-31 23:11 | MySQL Server: Memory storage engine | Closed (6226 days) | S1 | 5.0.38-BK, 5.0.27 | Linux (Linux) | Any | Update of a Field in a Memory Table ends with wrong result |
| 26979 | 2007-03-09 0:40 | 2007-03-09 1:47 | MySQL Server: Memory storage engine | Unsupported (6248 days) | S1 | 5.0.27 | Linux (Linux) | Any | locking of memory tables prevents 2nd tablename reference in the same query |
| 26080 | 2007-02-05 12:34 | 2007-03-15 13:23 | MySQL Server: Memory storage engine | Closed (6242 days) | S2 | MySQL Server: 5.1.14-beta-community-nt-l | Windows (Windows XP Home Edition, Linux) | Any | Memory Storage engine not working properly |
| 24985 | 2006-12-12 0:21 | 2007-04-05 19:42 | MySQL Server: Memory storage engine | Closed (6221 days) | S3 | 5.0.27/4.1BK/5.0BK/5.1BK | Windows (Windows 2K/Linux) | Any | UTF8 ENUM primary key on MEMORY using BTREE causes incorrect duplicate entries |
| 24052 | 2006-11-07 17:25 | 2006-12-18 18:56 | MySQL Server: Memory storage engine | Closed (6329 days) | S1 | 5.0.27/4.1:/5.1 | Windows (Windows 64) | Any | On Win64, MEMORY tables are limited to 4 GB |
| 23992 | 2006-11-05 23:10 | 2010-08-18 9:38 | MySQL Server: Memory storage engine | Not a Bug (6364 days) | S3 | 5.0.30-BK, 5.0.26 | Linux (Debian GNU/Linux Sid) | Any | "CREATE TABLE .. IF NOT EXISTS" confusion |
| 23764 | 2006-10-30 10:16 | 2006-11-28 12:28 | MySQL Server: Memory storage engine | Closed (6349 days) | S2 | 5.0.26 5.0.27 | Linux (FC5) | Any | BTREE index deletes only 1 item on memory table |
| 21846 | 2006-08-26 1:43 | 2006-09-05 14:32 | MySQL Server: Memory storage engine | Not a Bug (6433 days) | S3 | 5.0.25-BK, 5.0.24 | Linux (Linux, Windows) | Any | Query with memory table returns different results if indexed |
| 21031 | 2006-07-13 11:55 | 2006-10-26 13:38 | MySQL Server: Memory storage engine | Not a Bug (6382 days) | S3 | 5.0.21 | Any (any) | Any | Alter table to memory table defaults to hash indexes |
| 19138 | 2006-04-17 12:52 | 2007-05-03 6:02 | MySQL Server: Memory storage engine | Duplicate (6193 days) | S3 | 5.0.20, 5.0.19, 4.1.20 | Linux (Linux) | Any | The table 'foo' is full displayed on HEAP tables which shouldn't be full |
| 18233 | 2006-03-14 17:26 | 2006-05-24 18:25 | MySQL Server: Memory storage engine | Closed (6537 days) | S3 | 5.0.18 | Linux (Debian Linux) | Any | Memory tables INDEX USING HASH (a,b) returns 1 row on SELECT WHERE a= AND b= |
| 18160 | 2006-03-12 1:22 | 2006-06-03 13:35 | MySQL Server: Memory storage engine | Closed (6527 days) | S3 | 5.0.18, 4.1,x, 4.0.x | Linux (Debian Linux) | Any | Memory-/HEAP Table endless growing indexes |
| 12873 | 2005-08-30 10:30 | 2006-06-05 21:43 | MySQL Server: Memory storage engine | Closed (6525 days) | S3 | 4.1.14/5.0 | Linux (linux) | Any | BTREE index on MEMORY table with multiple NULL values doesn't work properly |
| « Show Previous 30 Entries | Showing 31-60 of 61 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
