| Showing 1-30 of 36 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 21106 | 2006-07-18 8:08 | 2006-07-19 10:12 | MySQL Server: Documentation | Closed (6484 days) | S2 | 5.0.22 | Any (any) | Any | Compressed MyISAM table is read only and thus truncate should not be possible |
| 21497 | 2006-08-08 0:12 | 2014-03-20 0:16 | MySQL Server | Closed (5105 days) | S2 | 5.0,5.1 | Any | Any | DOUBLE truncated to unusable value |
| 23556 | 2006-10-23 17:20 | 2007-02-08 17:28 | MySQL Server: General | Closed (6280 days) | S2 | 5.0.26 | Any (all) | Any | TRUNCATE TABLE still maps to DELETE |
| 25296 | 2006-12-27 18:05 | 2007-04-27 12:24 | MySQL Cluster: Disk Data | Closed (6202 days) | S2 | 5.1.14 | Linux (Linux 2.6) | Any | Truncate table converts NDB disk based tables to in-memory tables. |
| 25264 | 2006-12-24 12:06 | 2006-12-25 9:34 | MySQL Server: Stored Routines | Duplicate (6325 days) | S2 | 5.0.30 | Any (Any) | Any | ON DELETE triggers fire on TRUNCATE of InnoDB tables |
| 27984 | 2007-04-20 14:06 | 2007-06-18 19:41 | MySQL Server: Data Types | Closed (6150 days) | S2 | 5.0.27/5.1 | Linux (Redhat) | Any | Long Decimal Maths produces truncated results |
| 26438 | 2007-02-16 2:18 | 2007-03-16 10:22 | MySQL Server: Charsets | No Feedback (6244 days) | S3 | 5.0.32 | Linux (gentoo-linux-x86_64) | Any | invalidate character result in truncated data when inserting to gbk table |
| 29349 | 2007-06-26 1:01 | 2014-02-02 14:12 | MySQL Server: Memory storage engine | Verified (6141 days) | S3 | 5.0.27 | Any | Any | dropping MEMORY table very slow |
| 29507 | 2007-07-03 3:58 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Closed (5052 days) | S3 | 5.0.44 | Windows (Vista) | Any | TRUNCATE shows too many rows affected |
| 30889 | 2007-09-07 9:59 | 2008-02-01 17:57 | MySQL Server: General | Closed (5922 days) | S1 | 6.0.3, 5.0.50, 5.1.23 | Any | Any | filesort and order by with float/numeric crashes server |
| 28755 | 2007-05-29 16:38 | 2007-08-21 8:28 | MySQL Cluster: Disk Data | Closed (6086 days) | S2 | 5.1.18 | Any | Any | Truncating disk-based table crashes data nodes |
| 34677 | 2008-02-19 21:33 | 2008-03-01 12:32 | Connector / J | Closed (5893 days) | S2 | 5.1.5 | Any | Any | Blob.truncate throws exception with len < 1, should be < 0 |
| 35318 | 2008-03-16 11:14 | 2008-03-16 18:49 | MySQL Server: Errors | Closed (5878 days) | S3 | 5.1.23-rc-community | Windows | Any | Wrong number of affected rows in truncate |
| 37531 | 2008-06-19 19:38 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Closed (5052 days) | S3 | 5.1.25/6.0 | Any | Any | After truncate, auto_increment behaves incorrectly for InnoDB |
| 34087 | 2008-01-27 4:27 | 2008-01-27 22:53 | MySQL Server: Falcon storage engine | Can't repeat (5927 days) | S5 | 6.0.3-alpha | Any | Any | Truncate is extremely slow for Falcon tables |
| 36763 | 2008-05-16 18:45 | 2011-02-16 23:43 | MySQL Server: Replication | Closed (5541 days) | S3 | 5.1.24, 6.0 BK | Any | Any | TRUNCATE TABLE fails to replicate when stmt-based binlogging is not supported. |
| 47855 | 2009-10-06 10:09 | 2009-10-06 11:03 | MySQL Server: General | Not a Bug (5309 days) | S2 | 5.1.39 Community | Windows | Any | TRUNCATE TABLE having effect on transactional blocks |
| 48350 | 2009-10-27 14:13 | 2011-02-16 23:44 | MySQL Server: Row Based Replication ( RBR ) | Closed (5149 days) | S2 | 5.1.37, 5.1.40-enterprise-gpl-advanced-log, 5.1.41 | Linux | Any | truncate temporary table crashes replication |
| 54916 | 2010-06-30 14:24 | 2011-02-16 23:44 | MySQL Server: DML | Closed (4957 days) | S3 | 5.5.4-m3-log, 5.5.6-m3 | Any (FreeBSD 7.2, Mac OS X, Ubuntu) | Any | GROUP_CONCAT + IFNULL truncates output |
| 56597 | 2010-09-06 14:15 | 2011-02-16 23:44 | MySQL Workbench: SQL Editor | Closed (4951 days) | S3 | 5.2.27 | Windows (Windows 7) | Any | TRUNCATE command triggers 'safe updates' warning |
| 56536 | 2010-09-03 13:10 | 2010-10-05 16:12 | MySQL Server: InnoDB storage engine | Not a Bug (4945 days) | S3 | 5.1.43 | Linux | Any | CREATE TABLE … doesn't initialize data_length, index_length |
| 65615 | 2012-06-14 11:32 | 2012-06-15 3:57 | MySQL Server: Command-line Clients | Closed (4326 days) | S3 | 5.6.5 m8 | Linux (CentOS5.8 32bit) | Any | after truncating the table,data insert is slow |
| 71161 | 2013-12-17 11:58 | 2013-12-31 19:15 | MySQL Server: Errors | Not a Bug (3762 days) | S3 | 5.5.27-log | Linux | Any | Truncate function inconsistent |
| 71070 | 2013-12-04 4:05 | 2014-07-28 9:37 | MySQL Server: Replication | Closed (3628 days) | S2 | 5.6.14,5.5.18, 5.6.15 | Any | Any | kill of truncate table will lead to binary log written while rows remains |
| 71173 | 2013-12-18 14:57 | 2014-02-25 18:29 | MySQL Server: InnoDB storage engine | Closed (3706 days) | S2 | 5.7.3 | Windows (Windows 7 Enterprise 64-bit) | Any | MySQL 5.7.3 InnoDB multiple errors: 'chsize' returned OS error 71 |
| 72080 | 2014-03-19 18:06 | 2015-04-27 14:15 | MySQL Server: InnoDB storage engine | Closed (3343 days) | S1 | 5.6.15 | Any | Any | truncate temporary table crash: !DICT_TF2_FLAG_IS_SET(table, DICT_TF2_TEMPORARY) |
| 77064 | 2015-05-18 8:43 | 2015-07-27 12:10 | MySQL Server: Documentation | Closed (3189 days) | S3 | 5.5, 5.6 | Any | Any | Manual does not say anything about a known performance problem with TRUNCATE |
| 81208 | 2016-04-27 8:22 | 2016-05-19 0:34 | MySQL Workbench: SQL Editor | Closed (2892 days) | S2 | 6.3.6.511 | Windows (7) | Any | Workbench truncates hexadecimal values when showing CREATE VIEW code |
| 91387 | 2018-06-24 3:29 | 2018-07-02 8:53 | MySQL Server: InnoDB storage engine | Can't repeat (2118 days) | S1 | 5.6.30 | CentOS | x86 | mysql crash, Assertion failure in file srv0srv.cc line 1756 |
| 76956 | 2015-05-06 14:34 | 2018-10-31 7:36 | MySQL Server: Performance Schema | Verified (3271 days) | S2 | 5.6, 8.0.13 | Any | Any | Threads table PROCESSLIST_INFO truncate query |
| Showing 1-30 of 36 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
