| Showing 1-30 of 44 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Type | Status | Sev | Version | Target | OS | Summary | Assigned |
|---|---|---|---|---|---|---|---|---|---|
| 64940 | 2012-04-11 9:25 | Server: Memory | Closed (44 days) | S2 | 5.5.19 | Microsoft Windows (2003 server (32bit)) | Memory table no longer falls back to MyISAM when full | ||
| 62548 | 2011-09-27 10:22 | Server: Memory | Verified (241 days) | S2 | 5.1.49, 5.1.58 | Linux (Ubuntu) | Different result from memory and myisam table | ||
| 61238 | 2011-05-20 4:17 | Server: Memory | Verified (371 days) | S3 | 5.1.58, 5.5 | Mac OS X | Hash indexes with a prefix length do not work | ||
| 58061 | 2010-11-08 20:04 | Server: Memory | Verified (527 days) | S1 | 5.1.53, 5.5.8 | Any | crash with group_concat + too small myisam_data_pointer_size + partition | Mattias Jonsson | |
| 57725 | 2010-10-26 4:20 | Server: Memory | Not a Bug (561 days) | S2 | 5.1.51 | Any | Memory Storage Engine not to keep the auto_increment value of table option | ||
| 55559 | 2010-07-26 14:15 | Server: Memory | Duplicate (668 days) | S2 | 5.1, trunk | Any | MAX_HEAP_TABLE_SIZE does not work as specified | ||
| 53723 | 2010-05-18 0:44 | Server: Memory | Closed (737 days) | S2 | 5.1.40 | Mac OS X (10.6.3 Server & Client) | MEMORY table rows randomly disappear | ||
| 52924 | 2010-04-18 4:26 | Server: Memory | Can't repeat (672 days) | S2 | 5.0.18 | Any | Memory leak in MySQL version 5.0.18 | ||
| 51763 | 2010-03-05 10:11 | Server: Memory | Verified (812 days) | S3 | 5.1.31, 5.1.32, 5.1.37-2-log, 5.1.43, 5.1.45-bzr | Linux (Debian, Fedora) | Can't delete rows from MEMORY table with HASH key | ||
| 48196 | 2009-10-21 3:47 | Server: Memory | No Feedback (916 days) | S3 | 5.0.84 | Linux (SUSE SLES10.2) | Got error 134 when reading table(ENGINE=MEMORY) | ||
| 47704 | 2009-09-29 9:13 | Server: Memory | Closed (80 days) | S2 | 5.0.86, 5.1.39 | Linux | hash index on VARCHAR prefix not working correctly | ||
| 45137 | 2009-05-27 15:24 | Server: Memory | No Feedback (1063 days) | S2 | 5.1.32 | Sun Solaris | unable to limit total memory consumption | ||
| 44771 | 2009-05-11 2:27 | Server: Memory | Closed (527 days) | S2 | 5.1.34, 4.1, 5.0, 5.1, 6.0 bzr | Any | Unique Hash index in memory engine will give wrong query result for NULL value | Nirbhay Choubey | |
| 44138 | 2009-04-07 22:48 | Server: Memory | Open (322 days) | S2 | 5.1.57 | Linux (x86_64 rhel5 version from download page) | Memory engine table full at much less than max_heap_table_size with btree index | Sveta Smirnova | |
| 42868 | 2009-02-15 20:00 | Server: Memory | Verified (1195 days) | S3 | 5.0.74, 5.1.48 | Any | unique prefixed indexes on varchar columns don't work in memory engine | ||
| 41549 | 2008-12-17 14:27 | Server: Memory | No Feedback (1198 days) | S2 | 4.0.27-max-log | Linux (Debian Etch) | MySQL crashes with segmentation fault in ha_heap::rnd_next() | ||
| 39918 | 2008-10-07 22:59 | Server: Memory | Closed (1065 days) | S2 | 5.0.67, 5.1.30-bzr | 5.0+ | Any | memory (heap) engine crashing with b-tree index and DELETE with seg fault | Anurag Shekhar |
| 39886 | 2008-10-06 15:12 | Server: Memory | Closed (1205 days) | S3 | 5.0,5.1 | 5.1+ | Any | Table full for MEMORY table is not written into error log | Satya B |
| 39766 | 2008-10-01 2:31 | Server: Memory | Not a Bug (1310 days) | S2 | 5.0.60-log, 5.0.66a, 5.1.28 | Any | Physical order of rows in table alters update behavior of unique index | ||
| 37785 | 2008-07-01 21:47 | Server: Memory | Not a Bug (1423 days) | S3 | mysql-6.0-backup, mysql-maria | Linux | Order by works different for Memory storage engine | Sveta Smirnova | |
| 33473 | 2007-12-21 21:35 | Server: Memory | Not a Bug (1616 days) | S3 | 5.1.22 | Mac OS X | MEMORY engine doesn't honor MAX_ROWS correctly | ||
| 31445 | 2007-10-08 12:12 | Server: Memory | Duplicate (1677 days) | S2 | 5.0.45 | Microsoft Windows (Linux) | Delete only deletes first matching record | Takeover System Account | |
| 30885 | 2007-09-07 7:17 | Server: Memory | Closed (1675 days) | S2 | 5.0.50-bk | Any | MEMORY returns incorrect data if BTREE index is used for NULL lookup | Ramil Kalimullin | |
| 30590 | 2007-08-23 10:26 | Server: Memory | Closed (1677 days) | S1 | 5.0.48,5.1.22 | 5.1.23 | Any | delete from memory table with composite btree primary key | Sergey Vojtovich |
| 30293 | 2007-08-08 7:00 | Server: Memory | Not a Bug (1742 days) | S3 | 5.1.20, 5.0 , 4.1 BK | Any | memory tables with btree indexes .. very weird situation | Timothy Smith | |
| 30197 | 2007-08-02 6:35 | Server: Memory | No Feedback (1727 days) | S1 | 5.0.14 | Microsoft Windows (XP SP2) | mysqlnt memory access violation error | ||
| 30090 | 2007-07-27 6:23 | Server: Memory | Duplicate (1634 days) | S3 | 5.0.44 | Any | DELETE from MEMORY table with BTREE primary key extremely slow | Takeover System Account | |
| 29349 | 2007-06-26 1:01 | Server: Memory | Verified (1794 days) | S3 | 5.0.27 | Any | dropping MEMORY table very slow | ||
| 29342 | 2007-06-25 17:33 | Server: Memory | No Feedback (1766 days) | S3 | 5.1.14-beta | Microsoft Windows | Unsupported query executed by Brighthouse(storage engine) with no error message. | ||
| 29168 | 2007-06-18 9:07 | Server: Memory | No Feedback (1613 days) | S3 | 5.1 bk | Any | Error: Freeing pointer out of range at line 148, 'hp_block.c' |
| Showing 1-30 of 44 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
