Showing all 26 (Edit, Save, CSV, Feed) |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
21646 | 2006-08-15 6:04 | 2006-10-06 15:44 | MySQL Server: Views | Closed (6411 days) | S2 | 5.0.25-BK, 5.0.24-standard | Linux (Linux, REDHAT 9) | Any | ALGORITHM=MERGE CREATE VIEW FAILS FOR INNER JOINS WITH SUBQUERIES USING AGG FUNC |
26523 | 2007-02-21 13:03 | 2007-03-02 14:40 | MySQL Cluster: Cluster (NDB) storage engine | Can't repeat (6264 days) | S2 | 5.0.27 | Linux (Linux FC4) | Any | Randon "error while unpacking from engine" when MySQL-Max is installed. |
30580 | 2007-08-22 23:26 | 2007-08-23 20:42 | MySQL Server: Data Types | Closed (6090 days) | S3 | 4.1.11-Debian_4-log | Any | Any | max() is broken with unsigned data types |
33060 | 2007-12-07 12:18 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (5635 days) | S1 | 5.1.22-rc | Linux (Debian 4.0, mysql from src) | Any | Crash on subselect with MAX() |
34091 | 2008-01-27 15:14 | 2008-01-28 5:23 | MySQL Server | Not a Bug (5932 days) | S1 | 5.0.41 | Other (POWERBUILDER-7.0) | Any | 5.0.41-MAX |
37624 | 2008-06-25 10:26 | 2008-06-25 11:39 | MySQL Server: MyISAM storage engine | Not a Bug (5783 days) | S3 | 5.0 | Any | Any | query produces incorrect results witch float values |
39371 | 2008-09-10 13:37 | 2008-09-10 15:33 | Connector / ODBC | Closed (5706 days) | S1 | 5.1 | Windows | Any | In powerbuilder 9 User variables does not work with aggregate functions |
40037 | 2008-10-15 9:34 | 2011-10-20 3:46 | MySQL Server: Optimizer | Closed (4571 days) | S3 | 5.x, 6.x | Any | Any | Incorrect result from MIN/MAX when no GROUP, and independent subquery predicate |
41886 | 2009-01-05 20:53 | 2009-01-06 11:54 | MySQL Server: General | Not a Bug (5588 days) | S3 | 4.1.22, 5.0.67 | Linux | Any | max() and min() functions truncate result to 14 places on double columns |
42114 | 2009-01-14 15:06 | 2022-09-04 20:45 | MySQL Server | Duplicate (4635 days) | S2 | 5.1.30 | Linux (FC6) | Any | aggregation function with a null criterion and indexing returns wrong data |
45300 | 2009-06-03 11:52 | 2022-12-04 20:45 | MySQL Server: Data Types | Verified (4773 days) | S3 | 5.1.37 | Any | Any | MAX() and ENUM type |
46396 | 2009-07-27 9:20 | 2011-02-16 23:44 | MySQL Server | Can't repeat (5385 days) | S2 | 5.1.11 | Windows | Any | returned MAX value of primary integer key is less than actual max value |
45686 | 2009-06-23 16:36 | 2011-02-16 23:44 | MySQL Server: Data Types | Won't fix (5417 days) | S2 | 4.1, 5.0, 5.1 bzr | Any (MS Windows, Linux) | Any | Double min or max values rounding error |
48960 | 2009-11-21 13:25 | 2011-02-16 23:44 | MySQL Server: Compiling | Can't repeat (5267 days) | S1 | 5.1.39 | Linux (Fedora 12 x86) | Any | Compile from src.rpm with Federated or max config fails on Fedora 12 x86 |
50190 | 2010-01-08 16:39 | 2018-09-09 20:45 | MySQL Server: Optimizer | Duplicate (5190 days) | S3 | 6.0-codebase,pe,next-mr | Any | Any | MAX() and MIN() failing for time values with Innodb |
47631 | 2009-09-24 18:19 | 2011-02-16 23:44 | MySQL Server: Documentation | Closed (5218 days) | S2 | 4.1, 5.0, 5.1, next | Any (MS Windows 2003, Linux) | Any | Inconsistent reporting of date and time when subtracting MIN/MAX |
55626 | 2010-07-29 13:20 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (4881 days) | S3 | all | Any | Any | MIN and MAX reading a delete-marked record from secondary index |
54784 | 2010-06-24 16:51 | 2020-05-03 20:45 | MySQL Server: General | Duplicate (5036 days) | S3 | 5.5.3-m3-community, 5.5.6-m3 | Any (Win 7 (6.1.7600), Mac OS X) | Any | MIN(datetime), MAX(datetime) do not work |
57255 | 2010-10-05 16:27 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (4895 days) | S2 | 5.1.51-community | Any (MS Windows 7, Linux) | Any | Cascade Delete results in "Got error -1 from storage engine" |
63457 | 2011-11-28 16:29 | 2012-08-30 22:37 | MySQL Workbench | Closed (4256 days) | S3 | 5.2.35 rev 7915 | Linux (Ubuntu 11.04 x64) | Any | MySQL Workbench gives the wrong result when doing a MAX over a BIT field |
27199 | 2007-03-16 5:03 | 2013-09-09 9:28 | MySQL Server: Optimizer | Closed (3881 days) | S2 | 5.0.22, 5.0.37, 4.1 BK, 5.1 BK | Linux (linux) | Any | Performance problem when query contains a left join against a subquery |
69590 | 2013-06-26 15:59 | 2018-03-14 20:53 | MySQL Server: DML | Closed (2234 days) | S3 | 5.5.32 | Any | Any | Problem using between with group by functions |
79808 | 2015-12-29 17:50 | 2016-03-09 15:20 | MySQL Server: Documentation | Closed (2969 days) | S3 | any | Any | Any | Manual does NOT explain when "Select tables optimized away" is possible (or not) |
88590 | 2017-11-21 12:06 | 2017-11-22 11:45 | MySQL Server: DML | Not a Bug (2346 days) | S3 | 5.7.20 | Ubuntu (17.10) | Any | max(id) from multiple tables returns unexpected result |
93254 | 2018-11-20 3:33 | 2019-04-17 22:22 | MySQL Server: JSON | Closed (1835 days) | S3 | 5.7.24, 8.0.13 | Ubuntu | Other (x64) | MAX treating Numbers as Strings when used in group by and JSON_UNQUOTE |
53588 | 2010-05-11 22:59 | 2021-04-16 7:39 | MySQL Server: DDL | Verified (2291 days) | S3 | 5.5/5.6/5.7/8.0 | Linux (Ubuntu, Synology OS) | Any | Blackhole : Specified key was too long; max key length is 1000 bytes |
Showing all 26 (Edit, Save, CSV, Feed) |