| Showing 1-30 of 377 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 39519 | 2008-09-18 14:40 | 2011-02-16 23:43 | MySQL Server: C API (client library) | Closed (5445 days) | S3 | 6.0-TRUNK | Any | Any | mysql_stmt_close() should flush all data associated with the statement |
| 42268 | 2009-01-22 13:15 | 2013-02-27 13:19 | MySQL Server: C API (client library) | Closed (4242 days) | S2 | 5.0+ | Any | Any | MYSQL::server_capabilities is 16-bit in the protocol, but 32-bit in the library |
| 32991 | 2007-12-05 9:32 | 2011-02-16 23:43 | MySQL Server: Command-line Clients | Closed (5543 days) | S2 | 5.1, 6.0 | Any | Any | mysqlimport --use-threads test fails on solaris |
| 35543 | 2008-03-25 8:40 | 2011-02-16 23:43 | MySQL Server: Command-line Clients | Closed (5228 days) | S2 | 6.0-BK | Any | Any | mysqlbinlog.cc does not properly work with tmp files |
| 59153 | 2010-12-24 9:06 | 2011-02-16 23:44 | MySQL Server: Command-line Clients | Closed (5002 days) | S3 | 5.6.1 | Any | Any | mysqltest produces a valgrind warning when the running test fails |
| 15981 | 2005-12-26 10:36 | 2015-08-10 14:33 | MySQL Server: mysqldump Command-line Client | Can't repeat (6678 days) | S3 | 5.0.19-BK | Linux (Linux) | Any | mysqldump dumps triggers in incorrect format |
| 30027 | 2007-07-25 9:49 | 2015-08-10 14:33 | MySQL Server: mysqldump Command-line Client | Closed (6278 days) | S3 | 5.1 | Any | Any | mysqldump does not dump views properly |
| 30123 | 2007-07-30 10:51 | 2015-08-10 14:33 | MySQL Server: mysqldump Command-line Client | Closed (6256 days) | S1 | 5.1.21-BK | Any | Any | mysqldump from 5.1.21 doesn't work with 5.1.20 & earlier servers |
| 12673 | 2005-08-19 12:38 | 2006-08-17 10:54 | Instance Manager | Closed (6628 days) | S3 | 5.0 | Linux (Linux) | Any | Instance Manager: allows to stop the instance many times |
| 12674 | 2005-08-19 12:38 | 2006-03-04 0:25 | Instance Manager | Closed (6794 days) | S3 | 5.0 | Any | Instance Manager: IM doesn't handle client connections correctly | |
| 12813 | 2005-08-25 19:31 | 2006-02-28 2:48 | Instance Manager | Closed (6798 days) | S3 | 5.0 | Any | Instance Manager: START/STOP INSTANCE commands accept a list as argument | |
| 12814 | 2005-08-25 19:43 | 2007-12-06 15:28 | Instance Manager | Won't fix (6152 days) | S4 | Any | Any | Nonguarded option should be splitted into two ones | |
| 19043 | 2006-04-12 10:43 | 2015-03-22 20:45 | Instance Manager | Duplicate (6311 days) | S2 | 5.1.10-beta-BK | Windows (Windows) | Any | IM aborts if mysqld-path is not valid |
| 19044 | 2006-04-12 11:01 | 2007-01-16 20:53 | Instance Manager | Closed (6476 days) | S3 | 5.0 | Windows (Windows) | Any | IM aborts on exit |
| 20716 | 2006-06-27 9:11 | 2006-08-14 21:20 | Instance Manager | Closed (6631 days) | S3 | 5.0 | Any | SHOW INSTANCES statement causes races in IM tests | |
| 20761 | 2006-06-28 20:55 | 2007-10-05 15:17 | Instance Manager | Unsupported (6214 days) | S3 | 5.0.23 | FreeBSD (FreeBSD) | Any | Instance Manager: Signals are not handled correctly |
| 21783 | 2006-08-22 13:35 | 2007-04-06 14:12 | Instance Manager | Closed (6396 days) | S3 | 5.0.25 | Linux (Linux) | Any | Instance Manager does not exit on fatal error |
| 21884 | 2006-08-28 18:33 | 2007-10-05 15:17 | Instance Manager | Unsupported (6214 days) | S3 | 5.0.25BK | Any | Any | Instance Manager: PID file is created in non-atomic way |
| 22306 | 2006-09-13 12:48 | 2007-01-16 20:51 | Instance Manager | Closed (6476 days) | S3 | 5.1 | Any | STOP INSTANCE can not be applied for instances in Crashed, Failed and Abandoned | |
| 22308 | 2006-09-13 12:51 | 2007-10-05 15:19 | Instance Manager | Unsupported (6214 days) | S1 | 5.1 | Any | Any | Instance Manager does not support multiple options |
| 22428 | 2006-09-17 20:23 | 2007-10-05 15:19 | Instance Manager | Unsupported (6214 days) | S3 | 5.1/5.0 | Windows (Windows) | Any | Instance Manager: Invalid output of '--help' on Windows |
| 22467 | 2006-09-19 8:11 | 2007-10-05 15:19 | Instance Manager | Unsupported (6214 days) | S3 | 5.1 | Any (unix) | Any | IM fails to change configuration if the conf file path contains shell-patterns |
| 22472 | 2006-09-19 10:00 | 2006-10-26 3:34 | Instance Manager | Closed (6558 days) | S3 | 5.1 | Windows (Windows) | Any | IM: --socket option should be removed from Windows version |
| 22511 | 2006-09-20 8:54 | 2007-03-08 3:19 | Instance Manager | Closed (6425 days) | S3 | 5.0 | UNIX | Any | IM does not remove angel-pid-file on clean shutdown |
| 22588 | 2006-09-22 13:36 | 2007-10-18 10:28 | Instance Manager | Unsupported (6201 days) | S4 | 5.1 | Any | Any | Instance Manager: Avoid unnecessary quotes in SET statement |
| 22590 | 2006-09-22 13:45 | 2007-10-05 15:19 | Instance Manager | Unsupported (6214 days) | S2 | 5.1 | Any | Any | Instance Manager: Incorrect dumping of option values to the configuration file |
| 23215 | 2006-10-12 13:41 | 2007-01-16 20:49 | Instance Manager | Closed (6476 days) | S2 | 5.1.12 BK | Linux (Linux) | Any | STOP INSTANCE takes too much time |
| 23476 | 2006-10-19 19:01 | 2007-01-16 20:45 | Instance Manager | Closed (6476 days) | S1 | 5.1.12 BK | Any | DROP INSTANCE does not work | |
| 24475 | 2006-11-21 14:54 | 2007-10-05 15:20 | Instance Manager | Unsupported (6214 days) | S3 | 5.1 BK | Linux (Linux) | Any | Instance Manager: a memory leak |
| 24553 | 2006-11-23 19:21 | 2007-12-06 15:28 | Instance Manager | Won't fix (6152 days) | S4 | 5.0 BK | Any | Any | STOP INSTANCE: no way to tell if an instance was stopped successfully or not |
| Showing 1-30 of 377 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
