|
2014-03-21
| ||
| 18:16 | • Fixed ticket [07d6a045]: OFFSET ignored if there is no FROM clause plus 5 other changes (artifact: 9c43cbdc user: drh) | |
| 18:16 | Fix the OFFSET clause so that it works correctly on queries that lack a FROM clause. Ticket [07d6a0453d4ed8]. (check-in: 179ef816 user: drh tags: trunk) | |
| 18:04 | • New ticket [07d6a045] OFFSET ignored if there is no FROM clause. (artifact: c9ba18a7 user: drh) | |
| Ticket Hash: | 07d6a0453d4ed8dda32aae97005d1f3c0973844d | |||
| Title: | OFFSET ignored if there is no FROM clause | |||
| Status: | Fixed | Type: | Code_Defect | |
| Severity: | Minor | Priority: | Immediate | |
| Subsystem: | Unknown | Resolution: | Fixed | |
| Last Modified: | 2014-03-21 18:16:34 | |||
| Version Found In: | 3.8.4.1 | |||
| User Comments: | ||||
|
drh added on 2014-03-21 18:04:05:
The following SQL unexpectedly gives a single row of output: SELECT 1,2,3 LIMIT 1 OFFSET 25; This problem was discovered during internal testing and analysis and has not been observed in the wild. The problem is believed to have been in the code for a very long time. | ||||