Showing all 7 (Edit, Save, CSV, Feed) |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
30244 | 2007-08-05 17:52 | 2007-09-14 15:10 | MySQL Server | Closed (6062 days) | S3 | 5.0.48 5.1.21, 4.1 | Any | Any | row_count/found_rows does not replicate well |
31290 | 2007-09-28 22:59 | 2007-09-28 23:29 | MySQL Server: General | Not a Bug (6048 days) | S3 | 5.0.45 | Linux | Any | FOUND_ROWS() returns 1 for some queries |
39629 | 2008-09-24 14:23 | 2024-02-04 20:45 | MySQL Proxy: Scripts | Verified (5268 days) | S2 | r511 | Any | Any | Incorrect handling of LAST_INSERT_ID and FOUND_ROWS in rw-splitting.lua |
54868 | 2010-06-28 18:30 | 2011-02-16 23:44 | MySQL Workbench: SQL Editor | Closed (5013 days) | S3 | 5.2.24 CE RC Rev 6246 | Any | Any | SQL_CALC_FOUND_ROWS and FOUND_ROWS() do not work in MySQL Workbench SQL Editor |
68646 | 2013-03-12 2:52 | 2013-03-12 7:47 | MySQL Server: Optimizer | Duplicate (4056 days) | S3 | 5.6.10 | Windows (Server 2008 x64 SP2) | Any | SQL_CALC_FOUND_ROWS and FOUND_ROWS reporting incorrect values |
69119 | 2013-05-02 2:51 | 2013-06-03 14:26 | MySQL Server: Optimizer | Closed (3973 days) | S1 | 5.6.11 | Linux (CentOS 6.4) | Any | Wrong FOUND_ROWS() on MySQL 5.6.11 |
69144 | 2013-05-04 5:53 | 2013-05-04 10:55 | MySQL Server: DML | Duplicate (4003 days) | S2 | 5.6.11 | Any | Any | sql_calc_found_rows, found_rows() in 5.6.11 differs from 5.6.10 |
Showing all 7 (Edit, Save, CSV, Feed) |