| Showing 1-30 of 119 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 14145 | 2005-10-19 15:39 | 2006-07-14 19:15 | MySQL Server: Backup | Can't repeat (6873 days) | S3 | 5.0.15/5.0.16 BK source | Linux (Linux) | Any | mysqldump --routines creates non-reloadable output |
| 19660 | 2006-05-10 1:52 | 2006-11-13 4:45 | MySQL Server: Backup | Closed (6751 days) | S3 | 4.1,5.0,5.1 | Any | mysqldump --single-transaction should be with CONSISTENT SNAPSHOT | |
| 29643 | 2007-07-09 10:19 | 2008-10-18 15:32 | MySQL Server: Backup | Closed (6046 days) | S2 | 5.2.4 | IBM AIX (5.2) | Any | Backup: Link failure of executable mysqld, symbol in backup not found |
| 29861 | 2007-07-18 0:31 | 2007-07-23 9:19 | MySQL Server: Backup | Can't repeat (6499 days) | S2 | 5.0.18-log | Linux | Any | problems (many errors) using mysqlbinlog... | mysql ... |
| 30126 | 2007-07-30 17:14 | 2007-10-23 16:24 | MySQL Server: Backup | Closed (6407 days) | S3 | 5.0.45 | Linux | Any | ADD_DROP_DATABASE with mysqldump problem |
| 31020 | 2007-09-14 6:22 | 2007-10-12 17:36 | MySQL Server: Backup | Not a Bug (6418 days) | S3 | 5.1.21-beta-community | Any | Any | ARCHIVE tables with AUTO_INCREMENT ain't dumped in a backward compatible way |
| 31538 | 2007-10-11 15:36 | 2008-02-26 0:41 | MySQL Server: Backup | Closed (6281 days) | S2 | 5.2 | Any | Any | Backup file is too large. |
| 31963 | 2007-10-30 17:00 | 2008-08-21 18:20 | MySQL Server: Backup | Closed (6104 days) | S3 | 5.2 | Any | Any | Memory leaks in online backup code |
| 33224 | 2007-12-13 17:35 | 2007-12-14 22:48 | MySQL Server: Backup | Not a Bug (6355 days) | S3 | 5.1.22 | Any | Any | Events not exported |
| 33567 | 2007-12-29 0:32 | 2018-11-04 20:45 | MySQL Server: Backup | Duplicate (6030 days) | S3 | 6.0.5-alpha-debug | Linux (SUSE 10 64-bit) | Any | Backup: duplicate database names allowed |
| 34065 | 2008-01-25 18:43 | 2010-02-20 19:45 | MySQL Server: Backup | Closed (5556 days) | S3 | 6.0.5-alpha-debug | Linux (SUSE 10 / 64-bit) | Any | Backup: file names may be too short |
| 34067 | 2008-01-25 18:52 | 2012-05-18 20:19 | MySQL Server: Backup | Duplicate (5705 days) | S3 | 6.0.5-alpha-debug | Linux (SUSE 10 / 64-bit) | Any | Backup: restore failure if directory is not empty |
| 34480 | 2008-02-12 5:05 | 2018-11-04 20:45 | MySQL Server: Backup | Duplicate (6030 days) | S3 | 6.0.5-alpha-debug | Linux | Any | Backup: Backup to a file copies redundantly if database name is repeated. |
| 34694 | 2008-02-20 15:40 | 2012-05-18 20:19 | MySQL Server: Backup | Duplicate (6222 days) | S1 | 6.0.5 | Linux (64 bit) | Any | BACKUP: error messages are not being recorded to server error log |
| 35229 | 2008-03-11 20:36 | 2012-05-18 20:19 | MySQL Server: Backup | Duplicate (6266 days) | S3 | 6.0.5-alpha-debug | Linux (SUSE 10 | 32-bit) | Any | Backup: crash if backup |
| 35585 | 2008-03-26 21:28 | 2009-06-29 15:44 | MySQL Server: Backup | Closed (5792 days) | S3 | 6.0.5-alpha-debug-log | Linux (SUSE 10 | 32-bit) | Any | Online backup: Apparent synonyms for binlog start_position |
| 35891 | 2008-04-08 7:42 | 2008-05-08 12:47 | MySQL Server: Backup | No Feedback (6209 days) | S1 | 5.0.26 | Windows | Any | how to restore backup along with procedures and function |
| 36482 | 2008-05-02 23:20 | 2008-05-07 15:46 | MySQL Server: Backup | Duplicate (6210 days) | S2 | 5.0.54 | Linux (gentoo x86 kernel 2.6.20) | Any | mysqldump Dist 5.0.54 fail silently when trying to dump from 4.0.27 server |
| 36531 | 2008-05-06 13:06 | 2008-10-02 14:54 | MySQL Server: Backup | Closed (6062 days) | S3 | 6.0.5 | Any | Any | Backup: Objects can be restored in wrong order |
| 39375 | 2008-09-10 17:52 | 2009-02-11 3:26 | MySQL Server: Backup | Closed (5930 days) | S3 | 6.0.5 / 6.0.8 | Any | Any | Online backup crashes with simple combination of tables/triggers and SP |
| 46266 | 2009-07-17 15:04 | 2009-08-29 23:18 | MySQL Server: Backup | Closed (5731 days) | S2 | 5.4 | Windows | Any | RESTORE fails on a server with lower_case_table_names=2 |
| 55369 | 2010-07-19 15:32 | 2010-08-19 23:00 | MySQL Server: Backup | No Feedback (5376 days) | S1 | 5.0.45-community-nt | Windows (Windows XP) | Any | Importing dump.xml is not working |
| 63269 | 2011-11-15 19:59 | 2011-11-15 22:58 | MySQL Server: Backup | Can't repeat (4923 days) | S3 | 5.2.35 | Windows (windows 7) | Any | the mysql workbunch is not working after i installed it and work on it once |
| 69614 | 2013-06-28 16:55 | 2013-06-28 17:37 | MySQL Server: Backup | Unsupported (4332 days) | S1 | 5.6 | Windows | Any | Unable to do backup |
| 29082 | 2007-06-13 17:04 | 2007-06-14 20:54 | MySQL Server: Backup | Duplicate (6538 days) | S2 | 5.0.41 | Linux | Any | mysqlhotcopy skips file copy if database name is two alphanumberics long |
| 31077 | 2007-09-18 9:19 | 2007-11-15 14:47 | MySQL Server: Backup | Closed (6384 days) | S3 | 5.0.32 | Linux (Debian Etch) | Any | mysqldump appending date to dump breaks dump semantics |
| 31579 | 2007-10-13 14:23 | 2007-10-13 14:27 | MySQL Server: Backup | Duplicate (6417 days) | S2 | 5.0.37 | Windows | Any | Comments in triggers are not being restored after dump |
| 34577 | 2008-02-15 2:18 | 2008-02-15 10:00 | MySQL Server: Backup | Not a Bug (6292 days) | S3 | 6.0.5-alpha-debug | Linux | Any | Backup command doesn't error out, if the quotes aren't given for backup location |
| 48278 | 2009-10-24 9:48 | 2009-10-24 21:07 | MySQL Server: Backup | Can't repeat (5675 days) | S1 | 5.2 | Any | Any | InnoDB replication |
| 21215 | 2006-07-21 14:59 | 2006-08-15 3:12 | MySQL Server: Backup | Closed (6841 days) | S2 | mysqldump Ver 10.10 Distrib 5.0.22 | unknown-linux-gnu (x86_64) | Any | mysqldump creating incomplete backups without warning |
| Showing 1-30 of 119 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
