Showing 1-30 of 70 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
3521 | 2004-04-21 1:00 | 2004-06-11 20:42 | MySQL Server | Closed (7309 days) | S3 | 4.1.1-alpha | Other (tru64unix 5.1A, native compiler) | Any | "make test" status |
13056 | 2005-09-08 8:53 | 2005-09-22 10:00 | MySQL Server: Optimizer | Closed (6841 days) | S2 | MySQL 4.1.14-nt | Windows (Windows XP SP2) | Any | "SELECT DISTINCT" query with constant field |
19835 | 2006-05-16 1:57 | 2006-07-11 9:12 | MySQL Server: MyISAM storage engine | Closed (6549 days) | S1 | 5.0.22/4.1BK/5.0BK/5.1BK | Linux (Linux) | Any | Binary copy of corrupted tables crash the server when issuing a query |
8 | 2002-12-02 13:04 | 2002-12-02 17:02 | MySQL Server | Closed (7866 days) | S3 | 4.1.0 | Any (all) | Any | Bug in 4.1 distinct |
9269 | 2005-03-18 10:20 | 2005-04-26 0:30 | MySQL Server: Command-line Clients | Closed (6990 days) | S3 | 4.1.10a | Windows (windows 2k) | Any | bug in characterset / collation |
5304 | 2004-08-30 22:53 | 2004-10-01 13:30 | MySQL Cluster: Cluster (NDB) storage engine | Closed (7197 days) | S3 | 4.1.4-gamma (ndb) | Linux (SuSE 9.1) | Any | Cluster: index cardinality isn't the same as with MyISAM/InnoDB |
3904 | 2004-05-27 2:07 | 2004-06-09 23:37 | MySQL Server | Closed (7311 days) | S2 | 4.1.2 | Linux (Linux) | Any | COUNT DISTINCT performance anomaly in 4.1 |
3360 | 2004-04-01 10:22 | 2004-04-07 13:55 | MySQL Server | Closed (7374 days) | S2 | 4.1 | Any (all) | Any | count(distinct) crash server in prepared statements |
2633 | 2004-02-03 14:58 | 2004-02-20 5:48 | MySQL Server | Closed (7421 days) | S1 | 4.1 | Any (all) | Any | count(distinct) do not work with prepared statement |
16893 | 2006-01-30 11:36 | 2006-02-10 21:10 | MySQL Server | Closed (6700 days) | S1 | 4.1.18 | Other (OpenBSD) | Any | Crash in test 'fulltext_order_by' |
8614 | 2005-02-19 0:53 | 2005-06-22 2:29 | MySQL Server: Optimizer | Closed (6933 days) | S3 | 4.1.10 | Any (*) | Any | distinct sometimes ignored with group by "CONST" |
8616 | 2005-02-19 1:56 | 2005-03-21 20:04 | MySQL Server | Closed (7026 days) | S3 | 4.1.10 | Any | distinct with group by, suppresses rollup (and/or parts of result) | |
674 | 2003-06-18 12:14 | 2003-06-25 5:16 | MySQL Server | Closed (7661 days) | S1 | 4.0.13/14, 4.1.1 | Linux (Linux) | Any | DISTINCT ... DESC LIMIT cause "Lost connection..." |
6406 | 2004-11-03 17:07 | 2004-12-03 23:05 | MySQL Server | Closed (7134 days) | S1 | 4.1.8 + 5.0.2 | Linux (Linux) | Any | DISTINCT + SUBQUERY + ORDER BY crashes server |
29911 | 2007-07-19 19:39 | 2007-07-27 5:13 | MySQL Server: General | Closed (6168 days) | S2 | 5.0.45/4.1/5.1 | Linux | Any | DISTINCT adds a result to what should be an empty result set |
32798 | 2007-11-27 23:09 | 2008-01-28 17:41 | MySQL Server | Closed (5983 days) | S2 | 5.0.45/5.1/4.1 | Windows (Vista) | Any | DISTINCT in GROUP_CONCAT clause fails when ordering by a column with null values |
12887 | 2005-08-30 16:39 | 2005-09-15 19:35 | MySQL Server: Optimizer | Closed (6848 days) | S3 | 4.1.14, 5.0.11, 4.1.15-BK | Linux (Linux, freebsd, Windows) | Any | distinct vs rollup, are applied in inconsistent ways |
7079 | 2004-12-07 14:44 | 2004-12-13 13:39 | MySQL Server | Closed (7124 days) | S1 | 4.1.7-standard-log | Linux (SuSE Linux 9.1) | Any | DISTINCT with ANY/SOME subquery returns "Empty set" |
24856 | 2006-12-06 16:07 | 2007-05-08 0:40 | MySQL Server | Closed (6248 days) | S3 | 4.1.22 / 5.0.22, 5.1 BK | Linux (Linux) | Any | distinct with constant item and rollup => missing summary lines |
3681 | 2004-05-06 20:22 | 2004-05-17 12:24 | MySQL Server | Closed (7334 days) | S3 | 4.1.2 | Any | DISTINCT with ORDER BY does not returned ordered results | |
7946 | 2005-01-16 19:20 | 2005-02-04 21:04 | MySQL Server | Closed (7071 days) | S3 | 4.1.9 | Any | distinct with subquery and group by | |
9703 | 2005-04-07 2:26 | 2005-05-12 20:17 | MySQL Server: Optimizer | Closed (6974 days) | S2 | 4.1.11 | Linux (RedHat EL3) | Any | Error 1032 with GROUP BY query and large tables |
11704 | 2005-07-02 18:52 | 2011-02-16 23:43 | MySQL Server: Optimizer | Closed (5109 days) | S2 | 5.0.9, 4.1 | Linux (Linux/x86) | Any | Found locks from different threads in write -> crash with OPTIMIZE table? |
12095 | 2005-07-21 21:08 | 2005-08-08 15:44 | MySQL Server: Optimizer | Closed (6886 days) | S3 | 4.1.12-standard-log | Linux (linux) | Any | GROUP_CONCAT ingores the DISTINCT modifier |
5400 | 2004-09-03 21:15 | 2004-09-08 18:42 | MySQL Server | Closed (7220 days) | S2 | 4.1.4 | Windows (win2003) | Any | GROUP_CONCAT returns everything twice |
14217 | 2005-10-21 17:04 | 2005-10-24 11:45 | MySQL Server | Closed (6809 days) | S3 | 4.1.11-Debian_4sarge1-log | Windows (WindowsXP) | Any | GROUP_CONCAT with DISTINCT |
7405 | 2004-12-18 16:12 | 2005-06-01 3:08 | MySQL Server | Closed (6954 days) | S3 | 4.1.7 | FreeBSD (freebsd (probably others)) | Any | group_concat with distinct and rollup => ignores distinct in some rows |
757 | 2003-06-30 4:45 | 2003-07-06 12:39 | MySQL Server | Closed (7650 days) | S3 | 4.1 | Linux (Linux RedHat 9/Kernel 2.4.20) | Any | IFNULL cuts off result to second argument when using DISTINCT and subquery. |
25551 | 2007-01-11 16:30 | 2007-02-08 18:04 | MySQL Server: Optimizer | Closed (6337 days) | S3 | 4.1.22, 5.0.27, 5.0.34-BK | Linux (Linux, freebsd) | Any | inconsistent behaviour in grouping NULL, depending on index type |
52582 | 2010-04-04 3:51 | 2014-08-06 17:47 | MySQL Server: DML | Closed (4014 days) | S2 | 4.1.25, 5.0.91, 5.1.54, 5.5.10 | Any (IBM System i 32 bit, Linux) | Any | Incorrect results with COUNT DISTINCT and BIG_TABLES |
Showing 1-30 of 70 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |