This is the only way to get the information in a properly normalized database, except for the HUGE detail that using LIMIT ... OFFSET .. is suicide.
With a smart RDBMS you should get only 20 record in this case... (so yeah, hi mysql) but in the case of page 999999, you'll get enough results to fill all those pages to then throw away 99998.
Usually there's a way to force or teach automatic admin pages (because I think that's what this is) to avoid using LIMIT ... OFFSET ..., they should research their docs on how to do that (that normally in your kind of situation gets changed in "YOU should research the docs, find the example that explains in detail why they're useless moron and send the link to them cc: their boss" ;-) )<\/div><\/div>
<\/div>","width":640,"height":426}
With a smart RDBMS you should get only 20 record in this case... (so yeah, hi mysql) but in the case of page 999999, you'll get enough results to fill all those pages to then throw away 99998.
Usually there's a way to force or teach automatic admin pages (because I think that's what this is) to avoid using LIMIT ... OFFSET ..., they should research their docs on how to do that (that normally in your kind of situation gets changed in "YOU should research the docs, find the example that explains in detail why they're useless moron and send the link to them cc: their boss" ;-) )<\/div><\/div>
<\/div>","width":640,"height":426}