| Showing 1-30 of 71 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 21824 | 2006-08-25 7:19 | 2006-08-25 19:56 | MySQL Server | Duplicate (6447 days) | S1 | 5.0.24 (from ports) | FreeBSD (FreeBSD 6.1) | Any | LIMIT work incorrect |
| 22023 | 2006-09-05 14:38 | 2006-09-05 14:42 | MySQL Server | Not a Bug (6436 days) | S3 | 5.0.16 | Linux (Linux (FC4)) | Any | LIMIT and ORDER BY ordering error in SQL SELECT statement |
| 22506 | 2006-09-20 6:45 | 2006-11-26 16:36 | MySQL Server | No Feedback (6354 days) | S3 | 5.0.11 | Linux (Linux) | Any | Inncorrect order and missing records when order by date fields and limit |
| 22779 | 2006-09-28 12:18 | 2011-04-08 22:36 | MySQL Server: Optimizer | No Feedback (4760 days) | S5 | Ver 14.12 Distrib 5.0.24a | Windows (Windows 2000 server) | Any | "order by" clause performance.. |
| 24509 | 2006-11-22 15:09 | 2011-02-16 23:43 | MySQL Server: General | Closed (5057 days) | S3 | 5.0,5.1 | Windows (Windows) | Any | 2048 file descriptor limit on windows needs increasing |
| 28542 | 2007-05-20 17:51 | 2007-06-21 9:47 | MySQL Server | No Feedback (6147 days) | S3 | 4.1.13 | Any | Any | asc/desc query problem combined with limit and order by |
| 28937 | 2007-06-07 3:40 | 2007-06-07 7:38 | MySQL Server | Not a Bug (6161 days) | S3 | 5.0.44-BK, 5.0.22, 4.0.22 | Any | Any | SELECT statement does not produce SQL syntax error with trailing junk characters |
| 29095 | 2007-06-14 3:21 | 2010-05-09 3:28 | MySQL Server: General | Closed (6134 days) | S2 | 5.0.44-BK, 5.0.27 community, 5.0.41 Linux | Any (Windows/Linux same...) | Any | Insert into a select from a join b using(c) order by b.auto_id desc limit 1 fail |
| 30385 | 2007-08-13 10:07 | 2007-09-14 14:43 | MySQL Server: General | Closed (6062 days) | S2 | 5.0.24a, 5.1.20-beta, 4.1, 5.0, 5.1, 5.2 BK | Linux (ELsmp, Athlon Opteron dual core) | Any | Server crash when deleting with order by and limit |
| 30686 | 2007-08-29 9:37 | 2011-02-16 23:43 | MySQL Server: Optimizer | No Feedback (5434 days) | S2 | 5.1.20-beta-community-nt-debug, 5.1.30 | Windows ((via TCP/IP)) | Any | inappropriate LIMIT behavior on partitioned single-table query sorted by PK |
| 30858 | 2007-09-06 12:22 | 2012-09-13 8:34 | Connector / J | Not a Bug (4236 days) | S2 | 3.1, 5.0, 5.1 | Any | Any | ParameterMetaData.getParameterType(int i) returns wrong type for "LIMIT ?" |
| 30584 | 2007-08-23 3:31 | 2022-09-04 20:45 | MySQL Server: Optimizer | Duplicate (5566 days) | S5 | 5.0.37,5.1.22 | Any | Any | delete with order by and limit clauses does not use limit efficiently |
| 32933 | 2007-12-03 15:13 | 2008-01-11 17:04 | MySQL Server: Optimizer | Can't repeat (5943 days) | S2 | 5.0.52, 5.1.22-rc-community | Windows | Any | missing results with order by and limit in subquery in combination with indexes |
| 32071 | 2007-11-03 3:48 | 2007-11-28 16:29 | MySQL Server: Documentation | Closed (5987 days) | S2 | 4.0,4.1 | Any | Any | Account limits are not enforced per account |
| 34768 | 2008-02-22 21:19 | 2008-03-29 18:24 | MySQL Server: Replication | Closed (5865 days) | S2 | 5.1, 6.0 BK | Any | Any | nondeterministic INSERT using LIMIT logged in stmt mode if binlog_format=mixed |
| 35061 | 2008-03-05 2:25 | 2008-03-06 6:43 | MySQL Server: Optimizer | Duplicate (5888 days) | S3 | 5.0.50a | Linux | Any | order by returns unsorted results with limit and force index |
| 35206 | 2008-03-11 11:25 | 2008-04-07 17:32 | MySQL Server: Optimizer | Closed (5856 days) | S1 | 5.1.23 | Any | Any | select query result different if the key is indexed or not |
| 35209 | 2008-03-11 12:53 | 2008-03-19 13:32 | MySQL Server | Not a Bug (5875 days) | S2 | 5.0.45 | Linux (Trustix Secure Linux 3.0 / 2.6.19.2-1trsmp / glibc-2.3.5-10tr) | Any | maximum number of threads with MySQL binary RPMs |
| 35605 | 2008-03-27 13:40 | 2008-10-31 22:47 | MySQL Server: MyISAM storage engine | Duplicate (5649 days) | S2 | 5.1.23-ndb-6.3.10-telco | Linux (SuSE 9.3) | Any | ORDER BY `...` DESC LIMIT 1 return wrong row |
| 38576 | 2008-08-05 16:07 | 2008-08-05 19:20 | MySQL Server: Optimizer | Can't repeat (5736 days) | S2 | 5.1.23 | Linux (CentOS release 5 (Final)) | Any | Incorrect LIMIT behavior with ORDER BY |
| 38581 | 2008-08-05 18:59 | 2008-08-12 4:47 | MySQL Server: Command-line Clients | Not a Bug (5729 days) | S3 | 5.1.26 | Windows | Any | mysqlbinlog cannot read a DELETE FROM table LIMIT x; in the binary log |
| 39429 | 2008-09-12 21:01 | 2008-11-12 23:05 | MySQL Server: General | No Feedback (5637 days) | S3 | 5.0.45 | Windows (Server 2003) | Any | Retreive more rows with LIMIT than WITHOUT |
| 39078 | 2008-08-27 18:36 | 2008-08-29 16:29 | Connector / NET | Not a Bug (5712 days) | S3 | 5.1.7 | Windows | Any | LIMIT clause stops query parameter identification in Visual Studio |
| 41790 | 2008-12-30 3:35 | 2011-02-16 23:43 | MySQL Server: Optimizer | No Feedback (5558 days) | S5 | 5.0.51a | Linux | Any | Wrong optimization on large offsets for LIMIT clause |
| 39798 | 2008-10-02 0:06 | 2008-10-02 17:13 | Connector / J | Not a Bug (5678 days) | S2 | 5.1.6 | Any | Any | Limit 20,10 exceeds max result rows will return extra rows |
| 41980 | 2009-01-08 20:10 | 2011-02-16 23:43 | MySQL Server: Replication | Closed (5511 days) | S2 | 5.1.30, 5.1, 6.0 bzr | Any | Any | SBL, INSERT .. SELECT .. LIMIT = ERROR, even when @@SQL_LOG_BIN is 0 ! |
| 42019 | 2009-01-10 17:20 | 2011-02-16 23:43 | MySQL Server | Can't repeat (5401 days) | S1 | 6.0.8, 6.0.6 | Windows | Any | JOIN + LIMIT + SPECIAL WHERE in query sometimes makes it return wrong resultset |
| 43216 | 2009-02-26 9:13 | 2010-05-26 18:00 | MySQL Server: Falcon storage engine | Unsupported (5077 days) | S3 | 6.0.10 | Any | Any | Trailing values between 0x00 and the pad char sort incorrectly when using LIMIT |
| 42851 | 2009-02-13 22:27 | 2017-05-21 20:45 | MySQL Server: Replication | Duplicate (5251 days) | S3 | 5.1.31 | Linux (Fedora Core 9) | Any | Spurious "Statement is not safe to log in statement format." warnings |
| 45227 | 2009-05-31 22:48 | 2011-02-16 23:44 | MySQL Server: Optimizer | Closed (4897 days) | S3 | 5.4 | Any | Any | Queries with IN + condition, HAVING, ORDER BY 'pk' and LIMIT produce bad results |
| Showing 1-30 of 71 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
