Difference between revisions of "Issue:Offset should be implemented at SQL level, not PHP"
From FollowTheScore
Ycombarnous (talk | contribs) (New page: {{Issue |Type = Bug |Extension = DPL |Version = 1.5.1 |Description = Offset higher than max result limit outputs nothing |Status = open }} == Problem == If Max resu...) |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 4: | Line 4: | ||
|Version = 1.5.1 | |Version = 1.5.1 | ||
|Description = Offset higher than max result limit outputs nothing | |Description = Offset higher than max result limit outputs nothing | ||
| − | |Status = | + | |Status = closed |
}} | }} | ||
| Line 13: | Line 13: | ||
== Reply == | == Reply == | ||
| + | No reason for this, just my stupidness ;-). Maybe I find some time to change this by next week ... | ||
| + | :[[User:Gero|Gero]] 17:27, 31 October 2007 (CET) | ||
| + | |||
| + | Fixed with version 1.5.2 | ||
Latest revision as of 07:47, 3 November 2007
| Description: | Offset higher than max result limit outputs nothing |
| Extension / Version: | DPL / 1.5.1 |
| Type / Status: | Bug / closed |
Problem
If Max results for DPL is set to 500, looking for results in range 600-800 is impossible. The reason being that the offset is implemented at PHP level, not SQL level.
Any reason for this, as Mysql offers [LIMIT {[offset,] row_count | row_count OFFSET offset}]
Reply
No reason for this, just my stupidness ;-). Maybe I find some time to change this by next week ...
- Gero 17:27, 31 October 2007 (CET)
Fixed with version 1.5.2
